js2

Compare two test262 result files to find exactly which tests changed status. Use after a test262 run shows unexpected pass count changes.

Compile a source file to WAT and analyze the output for codegen inefficiencies. Use after a codegen change to verify the output is clean, when investigating performance issues, or when creating optimization issues from real compiler output.

Write an implementation spec for a hard issue. Read compiler source, identify exact functions/lines, design the fix, document edge cases.

Quickly find which commit introduced a test262 regression using git bisect with automated test.

Atomically claim an issue for a developer (human or agent) via the cross-developer lock ref, so two devs never pick up the same task. Syncs with origin first, refuses if already claimed or already done on main, and pushes the claim immediately without touching main or triggering CI.

Create a new issue file from a test262 failure pattern. Includes smoke test, sample extraction, and proper frontmatter.

Merge self-check for a green PR. Reads the PR's required-check status from the checks API (the committed ci-status feed is RETIRED), outputs MERGE (mark task completed, stand down — server-side auto-enqueue enqueues,

Protocol for detecting, isolating, and fixing regressions in test262 pass count. Use when a test run shows fewer passes than expected.

Triage N open PRs with sharded test262 results, rank by net pass delta, merge winners, close catastrophes. Use when multiple PRs have completed CI and you want to land a batch.

Find every open PR that is CONFLICTING/DIRTY against current main after a merge wave, ping its assigned dev to merge main into their branch and push, and track the re-test status.

Bulk-classify a list of test262 pass→other transitions from a CI run. Distinct from handle-regression (single fix) and analyze-regression (diff two runs). Use after a merge wave when the sharded run reports N regressions and you need to bucket them by root cause and decide which are false positives.

Sweep leaked ad-hoc dev scratch files (check-*.ts, debug-*.ts, test-*-debug.ts, tests/probe-*.test.ts, etc.) into .tmp/ so git status stays clean and token cost per tool call stays low.

End-of-session checkpoint — append diary, update active sprint doc with interim results/retro, write tech-lead handoff, commit and push. Use before /compact or at end-of-day. Distinct from sprint-wrap-up which closes a sprint.

Cleanly shut down a dev teammate — instruct them to write a context summary to plan/agent-context/{name}.md first, receive their approval, verify process exit. Use for scale-down, rotation, sprint wrap-up.

Quick validation of whether an issue still reproduces against current main. Use before dispatching to avoid wasting cycles on already-fixed issues.

Collaborative sprint planning — validate issues, prioritize, get architect/SM input, create task queue. Any agent can facilitate.

Run a sprint retrospective — gather data, analyze incidents, propose action items. Any agent can facilitate.

The tech lead's standing loop for keeping development unblocked across a sprint. Defines phase-by-phase protocol enforcement, merge-queue monitoring, and escalation triggers. Invoke at session start, again after every significant state change, and whenever devs look idle.

Dev self-merge pipeline — merge main into branch, equiv tests, CI wait, self-merge via /dev-self-merge. Run by devs, not a separate tester agent.

Show current test262 pass rates for both the js-host (gc) and standalone targets side by side, from committed baseline summaries — no network fetch, no compile. Use for a quick conformance status check.

End-of-sprint checklist — finalize results, clean up worktrees, update docs, prepare for retro. Any agent can run this.