What problem does it solve? Debugging often devolves into whack-a-mole fixes that patch symptoms while the real defect survives. This Skill enforces a disciplined five-phase workflow — investigate, analyze, hypothesize, implement, verify — so every fix is grounded in a confirmed root cause and backed by a regression test. ## Core Features & Use Cases - Root Cause First: An Iron Law blocks any fix until symptoms, code paths, and recent git history have been traced to a testable hypothesis. - Scope Lock: Optionally freezes edits to the affected directory so debugging never drifts into unrelated refactors. - Pattern Matching & 3-Strike Rule: Matches bugs against known patterns (race conditions, null propagation, stale cache) and escalates after three failed hypotheses instead of guessing. - Use Case: A user reports "checkout fails intermittently in staging." The Skill gathers the stack trace, checks recent commits to the payment module, confirms a race condition hypothesis with a temporary log, applies a minimal fix, and adds a regression test that fails without it. ## Quick Start Ask the assistant to investigate why your application throws an error and find the root cause before fixing it.
