systematic-debugging
Use for any bug, failing test, build/runtime failure, unexpected behavior, or performance regression; require reproduction, evidence, causal hypothesis, minimal experiment, root-cause fix, and regress
Files1
View on GitHubSKILL.md.agents/skills/systematic-debugging/SKILL.md
GitHubSystematic Debugging
No symptom patch before root-cause investigation.
- Read the first meaningful error/stack trace completely.
- Reproduce and write exact steps, inputs, environment, and frequency.
- Inspect recent changes and a similar working path.
- Trace state/data across component boundaries; add temporary diagnostics when needed.
- State one causal hypothesis:
X causes Y because evidence Z. - Test one variable with the smallest experiment.
- Once confirmed, create a failing regression test or deterministic reproduction.
- Implement one root-cause fix. Avoid opportunistic refactors.
- Run the narrow regression, then broader relevant checks, then runtime verification if applicable.
- After two blind fixes, stop guessing. After three failed causal fixes, reconsider architecture with the human.