Software Development
Systematic Debugging
You MUST use this whenever something is broken, before proposing or making any fix, including quick fixes and when the user is in a hurry: a bug, a failing or red test, a build or CI failure, a crash, a performance problem, unexpected behavior. Finds the root cause in four phases (investigate, compare, test one hypothesis, fix with a failing test first) instead of guessing, and stops after three failed fixes to question the design. Not for writing new features.
- Publisher / source
- davila7/claude-code-templates (found on skills.sh)
- Upstream record
- davila7/claude-code-templates
- Version
- Version 4
- Published
- Publication review
- Approved for publication
- Content fingerprint
98c593a96258d15ffcee71edb0f4743f9e90449c6412c46742b1ffc580db43c4