Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Point the issue-validation skill at the native test262 runner and pin file

Open Beginner friendly
  • Is something wrong?
#1,271 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
documentation, testing-qa

Research direction

Get the maintainer’s explicit approval before editing .agents/skills/gocciascript-issue-validation/SKILL.md. Read docs/test262.md and ADR 0120 first, then update the Test262 Validation steps to use GocciaTest262Runner and scripts/test262-suite-sha.txt while retaining scripts/run_test262_suite.ts only for supported tasks such as --merge-shards. Done means the skill matches the documented native runner and pin source.

Written by the indexing model from the issue text.

Description

documentation internal

Summary

.agents/skills/gocciascript-issue-validation/SKILL.md, "Test262 Validation", still tells agents to reproduce test262 issues with scripts/run_test262_suite.ts and GocciaScriptLoaderBare. It also says to read the pinned SHA from .github/workflows/pr.yml or ci.yml. Both are out of date:

  • docs/test262.md says test262 runs through the dedicated native GocciaTest262Runner (#1050, ADR 0120);
  • the pin lives in scripts/test262-suite-sha.txt.

Why

Agents following the skill reproduce test262 results through a different harness and pin source from the ones CI uses, so their results can disagree with the dashboard.

Current behavior

Step 2 says: "Use scripts/run_test262_suite.ts with GocciaScriptLoaderBare". Step 3 reads the SHA from the workflows, and step 4 builds loaderbare.

Expected behavior

The skill matches docs/test262.md:

  • reproduce with GocciaTest262Runner (build target and flags as documented);
  • read the pin from scripts/test262-suite-sha.txt;
  • keep scripts/run_test262_suite.ts only for what it still does, such as --merge-shards.

Scope notes

This is a project skill, so repository guidance says editing it needs the maintainer's explicit OK. This issue asks for that decision and the update. Found during release prep for 0.14.0.

Dominant language
Pascal
Stars
20
Forks
3
Avg merge
3d 21h
Merged PRs (30d)
51

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from frostney/GocciaScript

All issues in frostney/GocciaScript

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.