What problem does it solve? Random fixes and guess-and-check patching 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. - Evidence Gathering: Read error messages fully, reproduce issues consistently, check recent git changes, and trace data flow across component boundaries. - Rule of Three: After three failed fixes, stop and question the architecture instead of attempting a fourth patch. - Use Case: A failing pytest suite in production gets traced from the error message through recent commits and data flow to the exact source of the bad value, then fixed with a regression test proving the fix. ## Quick Start Use the systematic-debugging skill to investigate why this test is failing and find the root cause before proposing any fix.
