What problem does it solve? Random fixes and guess-and-check patches waste hours and introduce new bugs. This Skill enforces a disciplined four-phase debugging process that finds the root cause before any fix is attempted, preventing symptom-only patches and repeated failed fix attempts. ## Core Features & Use Cases - Four-Phase Process: Root cause investigation, pattern analysis, hypothesis testing, and implementation, each with explicit completion criteria. - Tight Feedback Loops: Builds fast, deterministic reproduction commands or tests that go red on the exact symptom and green when fixed. - Escalation Rules: The Rule of Three stops thrashing after three failed fixes and triggers an architectural review instead of a fourth guess. - Use Case: A failing pytest suite in production gets traced through error messages, git history, and data flow analysis to isolate the broken component, then a regression test is written before the single root-cause fix is applied. ## Quick Start Debug this failing test using the systematic-debugging process: find the root cause first, then write a regression test before fixing it.
