loopdive

loopdive/js2

Agent Claude Code

Software Architect for analyzing compiler internals and writing implementation specs in issue files. Spawn before dev work to plan hard issues.

loopdive/js2

Agent Claude Code needs its repo

Developer for implementing features, fixing bugs, and creating PRs. Use when code changes are needed for an issue — works in an isolated git worktree with a new branch.

loopdive/js2

Agent Claude Code needs its repo

Product Owner for backlog ownership, sprint planning, issue creation, acceptance, and stakeholder communication. Spawn for planning, review, or backlog grooming.

loopdive/js2

Agent Claude Code

Senior Developer for hard/architectural issues requiring deep compiler analysis. Use for issues with reasoningeffort max or feasibility hard.

loopdive/js2

Agent Claude Code

Tech Lead orchestrator — manages sprint dispatch, merges, and direct commits to main.

loopdive/js2

Command Claude Code needs its repo

Analyze the latest test262 run results, cross-reference with existing issues, and create new issues for unaddressed error patterns.

loopdive/js2

Skill Claude Code

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

loopdive/js2

Skill Claude Code

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.

loopdive/js2

Skill Claude Code

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

loopdive/js2

Skill Claude Code

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

loopdive/js2

Skill Claude Code needs its repo

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.

loopdive/js2

Skill Claude Code needs its repo

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

loopdive/js2

Skill Claude Code needs its repo

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.

loopdive/js2

Skill Claude Code

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

loopdive/js2

Skill Claude Code

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.

loopdive/js2

Skill Claude Code

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.

loopdive/js2

Skill Claude Code needs its repo

Cut and publish a versioned release of @loopdive/js2 + the js2wasm proxy — bump both manifests in lockstep, land a reviewed release PR, then push the vX.Y.Z tag that triggers npm/JSR publish. Use this whenever the user wants to release, publish, ship, cut, or tag a version, bump the version number, push a release tag…

loopdive/js2

Skill Claude Code needs its repo

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.

loopdive/js2

Skill Claude Code

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.

loopdive/js2

Skill Claude Code

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.

loopdive/js2

Skill Claude Code

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.

loopdive/js2

Skill Claude Code

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

loopdive/js2

Skill Claude Code

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

loopdive/js2

Skill Claude Code

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