debug · git:20260413.17c9c45 · 2026-04-13 · sha256 5f37e0c979bc1bfa
debug git:20260413.17c9c45A
Immutable. This exact content never changes and is served at /api/v1/blob/5f37e0c979bc1bfa.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_3gvbcgkjhxzzgyuz/5f37e0c979bc1bfa72fdccd3e79fd51e51ae0df3c559a6badec2b86af83bde39.json
Then /plugin install debug@markdownregistry-3gvbcgkjhxzzgyuz 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: debug description: "Systematic debugging. Use when a test fails, error occurs, or behavior is unexpected. Hypothesize → isolate → fix → verify." --- # Debug — Systematic Debugging ## Process ### 0. Recall - Query the knowledge graph: `mem_search` for the error message or file name - Check if a `resolution` or `pattern` node exists for this error category - If a past resolution exists, apply it directly instead of re-debugging from scratch ### 1. Observe - Read the full error message and stack trace - Identify: What was expected? What actually happened? - Note the exact file, line, and function ### 2. Hypothesize Form 2-3 possible causes. Rank by likelihood. ### 3. Isolate - **Narrow the scope**: Binary search through recent changes - **Reproduce minimally**: Smallest input that triggers the error - **Check assumptions**: Print/log intermediate values - **Bisect**: `git log --oneline -10` — when did it last work? ### 4. Fix - Fix the root cause, not the symptom - If the fix is a workaround, add a TODO with explanation ### 5. Verify - Run the failing test — must pass now - Run the full test suite — no regressions - If this was a bug, the regression test stays ### 6. Record - If the fix involved 3+ debug steps, record a `resolution` node via `mem_add` - Include: error category, root cause, solution approach - This enables future sessions to skip re-debugging the same class of issues ## When to Trigger - Any test failure during `/go` execution - Runtime error in tool output - "Unexpected" in any output ## Anti-Rationalization | Excuse | Rebuttal | What to do instead | |--------|----------|-------------------| | "Let me just try again" | Retrying without changing anything is not debugging. | Form a new hypothesis before each attempt. | | "It works on my machine" | Environment differences are bugs too. | Reproduce in the actual target environment first. | | "I'll just catch the exception" | That hides the bug, doesn't fix it. | Fix the root cause. Only catch what you can handle meaningfully. | | "It's probably a flaky test" | Flaky tests hide real bugs. Prove it's flaky before dismissing. | Run it 3x in isolation. If it fails consistently, it's real. | | "I'll add more logging" | Logging without a hypothesis is fishing. | Hypothesize first, then add targeted logging to confirm/deny. | ## Evidence Required Before claiming the bug is fixed, show ALL of these: - [ ] Root cause identified: one sentence explaining WHY it broke - [ ] Fix applied: diff showing the change - [ ] Previously failing test now passes (show output) - [ ] Full test suite passes (no regressions) - [ ] If bug came from a pattern, regression test added to prevent recurrence **"It works now" without root cause = symptom patch, not a fix.** ## Red Flags - Changing random things hoping something works - More than 3 retry attempts without forming a new hypothesis - Suppressing errors instead of fixing them