Setup & Installation
What This Skill Does
A structured debugging workflow that enforces root cause analysis before any fix is applied. It runs four phases: investigate, analyze, hypothesize, implement. The core rule is simple: no code changes until the root cause is confirmed.
Instead of patching symptoms and creating whack-a-mole bugs, this enforces a confirmed root cause before touching any code, which means fixes actually stick.
When to use it
- Tracing why a regression appeared after a recent commit
- Debugging intermittent failures that only show up in staging
- Finding the root cause of a null reference before patching it
- Running a structured post-mortem on a bug that keeps coming back
- Diagnosing configuration drift between local and production environments