What problem does it solve? Random fixes and guess-and-check patches waste time, mask underlying issues, and introduce new bugs. This Skill enforces a disciplined root-cause-first workflow so every fix addresses the actual cause instead of the symptom. ## Core Features & Use Cases - Four-Phase Process: Root cause investigation, pattern analysis, hypothesis testing, and implementation, each gated before the next begins. - Multi-Component Evidence Gathering: Trace data flow across component boundaries (CI, build, services, databases) using logs and non-mutating diagnostics. - Escalation Rules: After three failed fixes, stop and question the architecture rather than attempting a fourth patch. - Use Case: A CI build fails after a dependency update. Instead of tweaking configs blindly, reproduce the failure, check recent changes, form a single hypothesis, and verify one minimal fix at a time. ## Quick Start Use the systematic-debugging skill to investigate why the login integration test started failing after the last commit before proposing any fix.
