← ClaudeAtlas

debuglisted

Run /debug when something fails or behaves wrong: a failing test, a bug report, a /verify failure. Reproduces first, fixes the cause minimally, leaves a regression test. No features, no refactors.
rishabhsisodiya/stop-guessing · ★ 0 · Code & Development · score 70
Install: claude install-skill rishabhsisodiya/stop-guessing
## What this skill does Finds why something is broken, fixes that, and nothing else. Debugging goes wrong in two predictable ways. The first is fixing the symptom: the error stops appearing, the cause is still there, and it comes back somewhere less convenient. The second is the fix that grows: while in the file, three other things get tidied, and now the change cannot be reviewed or reverted. This skill is a loop with a hard edge around it. ## The loop ``` reproduce → localize → hypothesise → test the hypothesis → fix → verify → regression test ``` Never skip reproduce. Never skip verify. ## What this skill refuses to do 1. **Never fixes what it has not reproduced.** A fix for a bug you have not seen is a guess wearing a commit message. If it cannot be reproduced, say so and go no further; the report is what you learned and what you still need. 2. **Never fixes the symptom when the cause is reachable.** If the cause is out of scope or would take a redesign, say that explicitly, make the smallest safe containment, and put the real cause in the report. Never let a symptom fix pass as a resolution. 3. **Never refactors.** Not the function, not the file, not the "while I am here". A bug fix diff should be small enough to review in a minute. Improvements go in the report. 4. **Never changes a test to make it pass.** If a test is genuinely wrong, that is a finding to raise, not a line to edit quietly. A weakened assertion converts a real signal into a