What problem does it solve? Debugging often devolves into guessing and symptom-patching, which creates whack-a-mole bugs and regressions. This Skill enforces a disciplined four-phase debugging workflow that finds the actual root cause before any code is changed. ## Core Features & Use Cases - Root Cause First (Iron Law): No fixes are applied until a specific, testable root cause hypothesis is formed from symptoms, stack traces, code tracing, and git history. - Four-Phase Workflow: Investigate, analyze patterns (race conditions, null propagation, state corruption, config drift), test hypotheses with a 3-strike escalation rule, then implement a minimal fix with a regression test. - Scope Locking: Optionally freezes edits to the affected directory so debugging does not creep into unrelated code. - Use Case: A user reports "the checkout endpoint returns 500 intermittently." The Skill traces the code path, checks recent commits, identifies a race condition on shared state, confirms it with a temporary log, then ships a minimal fix plus a failing-then-passing regression test. ## Quick Start Ask the assistant to investigate why the login flow throws a 500 error after the latest deploy.
