systematic-debugging
Installation
SKILL.md
Methodology from obra/superpowers (MIT)
Systematic Debugging
Core rule: find the root cause before writing any fix.
Phase 1 -- Root Cause Investigation
- Reproduce the bug with the simplest possible input.
- Read the actual error message / stack trace. Do NOT guess.
- Trace the data flow backwards from the failure site to the origin.
- Identify the earliest point where observed behavior diverges from expected.
Phase 2 -- Pattern Analysis
- Search the codebase for similar patterns (same API, same data path).
- Check recent changes (git log, git blame) near the failure site.
- Look for related open issues or past fixes for the same component.
- Note if the bug is deterministic or intermittent -- intermittent implies concurrency, timing, or external state.