메뉴
Validate GocciaScript engine issues against the project-specific test262 harness. Use alongside implement-issue for GocciaScript issues that mention test262, ECMA-262/ECMA-402 conformance, Intl, or parser compatibility flags.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Commits relevant changes, pushes a focused branch, and opens a templated draft pull request. Use when the user runs /create-pr.
Reviews a roadmap from fresh project evidence and produces a verified, throughput-anchored version plan, with execution gated on confirmation. Use when reviewing a roadmap, planning releases, or sequencing a backlog.
Applies the user's ambient engineering bar: current evidence, complete in-scope solutions, reuse, real validation, right-sized value, and maintainability. Use for planning, implementing, debugging, reviewing, refactoring, architecture, or substantial technical investigation.
Investigates and creates a project-aligned GitHub issue from a tagline or short description, using the repository's template, evidence, and labels. Use when the user runs /create-issue or asks to file a GitHub issue.
Prepares a changelog-first release and, only when explicitly requested, publishes it through the repository's single established release path. Use when the user asks to prepare, cut, tag, or publish a release, bump the version, or generate release notes.
Applies the user's git defaults: branch from the remote default, merge rather than rebase, never amend or force-push, and squash-merge pull requests. Use when branching, syncing, committing, pushing, or merging in the user's repos.
| name | gocciascript-issue-validation |
| description | Validate GocciaScript engine issues against the project-specific test262 harness. Use alongside implement-issue for GocciaScript issues that mention test262, ECMA-262/ECMA-402 conformance, Intl, or parser compatibility flags. |
Project-specific validation rules for GocciaScript issues. Use this skill with the generic implement-issue workflow when the issue references test262, ECMAScript/ECMA-402 behavior, or compatibility flags.
For ECMA-262 or ECMA-402 semantics, use the pinned tc39-mcp@0.6.1 server from the project MCP config under .agents/mcp/ when it is available. tc39-mcp spec-reading tools default to ECMA-262, so pass the spec explicitly for the standard you are checking:
spec: "262"spec: "402"spec.search when the exact clause id is unknown, for example spec.search({ spec: "402", query: "Intl.DateTimeFormat" }) for Intl work.clause.get for the relevant clause before deciding expected behavior, for example clause.get({ spec: "402", id: "sec-intl.datetimeformat" }).spec.crossrefs when behavior depends on abstract operations or cross-spec references. For ECMA-402 algorithms that call ECMA-262 operations, start from spec: "402" and set include_cross_spec: true.spec.diff or spec.history with the same explicit spec when the issue may involve recent prose drift.test262.search to map a clause id or feature area to conformance tests.test262.get to inspect a specific conformance test when the MCP server returns one.proposal.list or proposal.get for proposal-stage features.Record the spec, edition, clause id, section number, and snapshot SHA when the MCP response provides one. If tc39-mcp is not available, fall back to the official TC39 sources (tc39.es/ecma262, tc39.es/ecma402) rather than guessing.
When an issue references test262 files, patterns, or categories:
docs/test262.md before running the reproduction.scripts/run_test262_suite.ts with GocciaScriptLoaderBare; do not run stock test262 files directly through GocciaScriptLoader, GocciaTestRunner, or hand-built wrappers..github/workflows/pr.yml or .github/workflows/ci.yml unless the issue explicitly targets another SHA../build.pas --clean loaderbare
Use the clean form after merges, branch switches, PR syncs, generated
resource changes, or any unexplained FPC/resource compiler failure. A plain
./build.pas loaderbare is only appropriate for tight iteration after a
known-clean build.
bun scripts/run_test262_suite.ts \
--suite-dir /path/to/test262-suite \
--categories intl402 \
--filter 'intl402/NumberFormat/prototype/format/example.js' \
--mode bytecode \
--jobs 1 \
--verbose
The runner supplies the compatibility flags, harness substitutions, non-strict script handling, timeout/memory limits, pinned harness behavior, and PASS/FAIL/WRAPPER_INFRA classification used by CI. Direct loader experiments are only supplemental after the project runner result is known.