Debug-Driven
A structured, hypothesis-driven debugging loop. Instead of immediately guessing a fix, this skill drives a disciplined hypothesis -> instrument -> reproduce -> analyze -> fix -> verify -> cleanup cycle.
Core Philosophy
Never guess. Instrument, observe, then fix.
The best debuggers do not immediately patch code. They:
- Form multiple hypotheses about what could be wrong
- Instrument the code to test each hypothesis with real runtime data
- Let the human reproduce
[Description truncada. Veja o README completo no GitHub.]