debug
Installation
SKILL.md
dot-skills Debugging Best Practices
The front door for a reported failure. It resolves the cheapest loop that reproduces the symptom, narrows to a cause, and either lands a fix or hands the case to the full loop. Debugging methodology: 54 rules across 10 categories prioritized by impact. Based on research from Andreas Zeller's "Why Programs Fail" and academic debugging curricula.
Contract
Inputs:
- A reported symptom: error text, a crash, wrong output, or a performance number that moved.
Outputs: