loopdive
@loopdive Organization
Public Skills
steward
by loopdive
Repo-specific PR/CI conventions for an agent subscribed to PR activity (loopdive/js2wasm). Read this BEFORE acting on a CI or review event. Overrides the generic PR-steward defaults where this repo's merge queue, gates and hooks make them wrong — most importantly: agents NEVER enqueue, a bot hold is a real regression, and close+reopen is the sanctioned way to DEQUEUE for a push.
publish-release
by loopdive
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, cut a patch/minor/major, cut release notes, or get a fix onto npm — even if they only say "ship it" or name a version like "0.70.0" without saying the word release. Also use it when a publish failed on verify-version, when a vX.Y.Z tag needs pushing or re-pushing, or when someone is about to run git tag vX.Y.Z by hand (that is the bug this skill exists to prevent).
suspend
by loopdive
Suspend ALL in-flight team work durably — snapshot every agent worktree, write a ## Suspended Work handoff into each lane's issue file, push every lane branch, open one DRAFT PR per lane with the handoff in the description, and disarm the loop's timers. Run before a planned stop, container teardown, or long pause. Resume is a fresh agent per lane reading the issue file's handoff.
dev-self-merge
by loopdive
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, #2786) or ESCALATE. Devs do NOT enqueue.
sprint-wrap-up
by loopdive
End-of-sprint checklist — finalize results, clean up worktrees, update docs, prepare for retro. Any agent can run this.
regression-triage
by loopdive
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.
analyze-wat
by loopdive
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.
claim-issue
by loopdive
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.
test-and-merge
by loopdive
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.
smoke-test-issue
by loopdive
Quick validation of whether an issue still reproduces against current main. Use before dispatching to avoid wasting cycles on already-fixed issues.
sprint-retrospective
by loopdive
Run a sprint retrospective — gather data, analyze incidents, propose action items. Any agent can facilitate.
analyze-regression
by loopdive
Compare two test262 result files to find exactly which tests changed status. Use after a test262 run shows unexpected pass count changes.
test262-pass-rates
by loopdive
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.
sprint-planning
by loopdive
Collaborative sprint planning — validate issues, prioritize, get architect/SM input, create task queue. Any agent can facilitate.
create-issue
by loopdive
Create a new issue file from a test262 failure pattern. Includes smoke test, sample extraction, and proper frontmatter.
bisect-regression
by loopdive
Quickly find which commit introduced a test262 regression using git bisect with automated test.
merge-wave
by loopdive
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.
tech-lead-loop
by loopdive
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.
scratch-cleanup
by loopdive
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.
architect-spec
by loopdive
Write an implementation spec for a hard issue. Read compiler source, identify exact functions/lines, design the fix, document edge cases.
shutdown-dev
by loopdive
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.
session-wrapup
by loopdive
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.
handle-regression
by loopdive
Protocol for detecting, isolating, and fixing regressions in test262 pass count. Use when a test run shows fewer passes than expected.
pr-conflict-refresh
by loopdive
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.