debugging-methodlisted
Install: claude install-skill rustcircle/c101
# Debugging method
Debugging is the scientific method under time pressure: observe, reproduce, form falsifiable
hypotheses, run the experiment that splits the hypothesis space best, and stop only at a cause you
can switch on and off. A fix without a reproduced failure is a guess.
## 0. The loop and its exit criteria
```
Intake -> Reproduce -> Minimize -> Localize -> Hypothesize <-> Experiment -> Fix -> Verify -> Prevent
```
Done means all of:
- [ ] A repro that fails before the fix and passes after it (N runs for intermittent bugs, section 8).
- [ ] A root-cause statement: the defect, the triggering condition, and why it produces the symptom.
- [ ] A regression test in the suite that fails without the fix.
- [ ] Sibling search done (same pattern elsewhere).
- [ ] Notes written (section 10) when the bug escaped to users or cost more than ~2 hours.
## 1. Intake
Collect before theorizing; write it at the top of the hypothesis log.
```markdown
Expected: <exact expected behaviour, with source: spec, test, doc>
Actual: <exact observed behaviour; paste the error verbatim, first and last 20 lines of trace>
Steps: <minimal known steps>
Environment: <versions: app SHA, runtime, OS, dependency lockfile hash, config, data snapshot>
Frequency: always | N of M runs | only under load | only in CI | only in prod
Last good: <version/date where it worked, if known> First bad: <...>
Artifacts: logs, core dump, HAR, screenshots, failing CI job URL
```
Read the error