fix-bug · git:20261108.f56f165 · 2026-11-08 · sha256 25263d9aba88ac81
fix-bug git:20261108.f56f165A
Immutable. This exact content never changes and is served at /api/v1/blob/25263d9aba88ac81.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ipvdb5ifequsadgc/25263d9aba88ac8147ca1d71f9e0decd8ea40813b69040adf855ba96284656fb.json
Then /plugin install fix-bug@markdownregistry-ipvdb5ifequsadgc in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: fix-bug description: Fix a bug the safe way - reproduce it as a failing test first, then fix, verify and report argument-hint: "<bug description or issue link>" disable-model-invocation: true --- Use the team skill to fix this bug: $ARGUMENTS 1. `tester` reproduces the bug as a failing regression test (verdict `REPRODUCED`). If it cannot, report what was tried and ask the user for details. 2. `backend-dev` or `frontend-dev` fixes the root cause until the test passes, touching only the files you assign. 3. `tester` verifies the fix and the callers that could regress; add `security-reviewer` when the bug is security-related. 4. Record the lesson under "Known traps" in the area card, update `STATE.md` and give the end-of-task report. For a trivial bug you may do the steps yourself, but the failing test still comes first.