debug-and-fix
Installation
SKILL.md
Debug and Fix
Purpose
This skill provides a structured approach to debugging: hypothesize, isolate, fix, verify, protect. It prevents the two most common debugging failure modes — fixing the symptom instead of the root cause, and fixing the root cause without preventing it from recurring.
Triage Before You Start
Not every "this is wrong" report is a bug. Classify the work first, using the canonical routing table:
| The report is… | Is it a bug? | Route to |
|---|---|---|
| Behavior that contradicts the spec, docs, or obvious intent | ✅ Yes | This skill |
| Working as designed, but the design is insufficient ("search works but results are bad") | ❌ No | idea-to-prd — that is a feature request |
| Correct but slow | ❌ No | performance-review for systemic slowness; a perf regression with a reproducible before/after is a bug and stays here |
| Ugly/confusing but functioning code | ❌ No | refactor |
| A vulnerability with no functional symptom | ❌ No | security-review to assess; the resulting fix work enters the pipeline |
The expected-vs-actual question usually settles it: a bug has a defensible expected behavior the system fails to meet. If "expected" turns out to be a new opinion about what the product should do, it is a feature.