debugging-and-error-recovery
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
Install
git clone https://github.com/addyosmani/agent-skills /tmp/agent-skills && ln -s /tmp/agent-skills/skills/debugging-and-error-recovery ~/.claude/skills/debugging-and-error-recoveryFrom README
Debugging and Error Recovery Overview Systematic debugging with structured triage. When something breaks, stop adding features, preserve evidence, and follow a structured process to find and fix the root cause. Guessing wastes time. The triage checklist works for test failures, build errors, runtime bugs, and production incidents. When to Use Tests fail after a code change The build breaks Runtime behavior doesn't match expectations A bug report arrives An error appears in logs or console Something worked before and stopped working The Stop-the-Line Rule When anything unexpected happens: Don't push past a failing test or broken build to work on the next feature. Errors compound. A bug in Step 3 that goes unfixed makes Steps 4-6 wrong. The Triage Checklist Work through these steps in order. Do not skip steps. Step 1: Reproduce Make the failure happen reliably. If you can't reproduce it, you can't fix it with confidence.
More from this repo
api-and-interface-design
Guides stable API and interface design.
constraint-driven-development
Establishes a project's quality bar as a written contract and stops agents quietly lowering it.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands.