What problem does it solve? Developers often apply quick patches or guess-and-check fixes without understanding why a bug occurred, which masks deeper issues, introduces regressions, and accumulates technical debt. This Skill enforces a disciplined investigation process so every fix addresses the actual root cause. ## Core Features & Use Cases - Four-Phase Debugging Workflow: Reproduce the issue, trace and classify the root cause (logic, state, contract, environment, regression), validate an explicit hypothesis with a failing test, then apply and verify a minimal fix. - Iron Law Enforcement: Blocks any code change until the root cause is identified with evidence, with rationalization tables that counter common excuses for skipping investigation. - Reference Guides: Includes root-cause tracing techniques (git bisect, stack trace analysis, 5 Whys) and defense-in-depth strategies for layered protection against recurring bug classes. - Use Case: When a login endpoint returns a 500 error in CI but works locally, use this Skill to reproduce the failure, trace the execution path, classify it as an environment issue, and ship a verified fix with a regression test. ## Quick Start Ask the AI to debug a specific error, for example: investigate why the auth module throws a TypeError on login and find the root cause before fixing it.
