What problem does it solve? Debugging often devolves into guessing and symptom-patching, creating whack-a-mole cycles where each fix spawns new bugs. This Skill enforces a disciplined five-phase workflow that finds the actual root cause before any code changes, then proves the fix works with regression tests. ## Core Features & Use Cases - Root Cause Investigation: Collects symptoms, traces code paths, checks recent git history, and reproduces the bug before forming any hypothesis. - Pattern Analysis & Hypothesis Testing: Matches bugs against known patterns (race conditions, null propagation, state corruption, integration failures) and applies a 3-strike rule that stops blind guessing and escalates when hypotheses fail. - Verified Fixes with Regression Tests: Requires a test that fails without the fix and passes with it, plus a structured debug report saved to memory for future sessions. - Use Case: A user reports an intermittent production error with a stack trace. The Skill traces the failure path, checks recent commits, confirms a race condition hypothesis with a temporary log statement, applies a minimal fix, and ships a regression test with a full debug report. ## Quick Start Investigate this error and find the root cause before proposing any fix, then verify the fix with a regression test.
