What problem does it solve? Debugging often devolves into guessing and symptom-patching, which creates recurring bugs and whack-a-mole fixes. This Skill enforces a disciplined workflow that finds the actual root cause before any code change is made. ## Core Features & Use Cases - Root Cause Investigation: Collects symptoms, traces code paths, checks recent git history, and reproduces the bug before forming a hypothesis. - Pattern Analysis & Hypothesis Testing: Matches bugs against known patterns (race conditions, null propagation, state corruption, integration failures) and verifies hypotheses 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, 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 failure path, checks recent commits, confirms a race condition hypothesis with logging, applies a minimal fix, and ships a regression test plus a debug report. ## Quick Start Ask the assistant to investigate this error and find the root cause before fixing it, pasting the stack trace or describing the unexpected behavior.