skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / Testing & QA / Systematic Debugging Skill by @obra
The skill is the skills/systematic-debugging folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Insists on finding the root cause before proposing fixes, using four phases with an 'iron law' against guessing. It is meant for any bug, test failure or unexpected behaviour.
The original SKILL.md is organised into these sections:
Written and maintained by @obra. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
-----|---------| | "Issue is simple, don't need process" | Simple issues have root causes too. Process is fast for simple bugs. | | "Emergency, no time for process" | Systematic debugging is FASTER than guess-and-check thrashing. | | "Just try this first, then investigate" | First fix sets the pattern. Do it right from the start. | | "I'll write test after confirming fix works" | Untested fixes don't stick. Test first proves it. | | "Multiple fixes at once saves time" | Can't isolate what worked. Causes new bugs. | | "Reference too long, I'll adapt the pattern" | Partial understanding guarantees bugs. Read it completely. | | "I see the problem, let me fix it" | Seeing symptoms ≠ understanding root cause. | | "One more fix attempt" (after 2+ failures) | 3+ failures = architectural problem. Question pattern, don't fix again. | ## Quick Reference | Phase | Key Activities | Success Criteria | |-------|---------------|------------------| …
Excerpt only, quoted from the author's repository. Open the repository for the complete file.