What problem does it solve? Debugging often devolves into guessing and symptom-patching, which creates whack-a-mole bugs that resurface later. This Skill enforces a disciplined five-phase workflow that finds the actual root cause before any fix is written, then proves the fix works with a regression test. ## Core Features & Use Cases - Structured Root Cause Investigation: Collects symptoms, traces code paths, checks recent git history, and reproduces the bug before forming any hypothesis. - Pattern Matching & Hypothesis Testing: Classifies failures into known patterns (race conditions, null propagation, state corruption, integration failures, configuration drift, stale caches) and verifies each hypothesis with temporary instrumentation, with a 3-strike stop rule. - Verified Fixes with Regression Tests: Requires a minimal-diff fix, a regression test that fails without the fix and passes with it, a full test suite run, and a structured debug report saved to memory. - Use Case: A user reports an intermittent production error with a stack trace. The Skill traces the code path, checks recent commits, identifies a race condition, confirms it with a temporary log statement, applies a minimal fix, and ships a regression test plus a debug report. ## Quick Start Ask the assistant to investigate and find the root cause of the error or bug you are experiencing before attempting any fix.
