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 debugging methodology that finds the root cause before any fix is attempted. ## Core Features & Use Cases - Four-Phase Process: Root cause investigation, pattern analysis, hypothesis testing, and verified implementation, with strict gates between phases. - Root Cause Tracing: Trace bugs backward through the call stack to find the original trigger instead of patching symptoms, plus defense-in-depth validation at every layer. - Flaky Test Elimination: Replace arbitrary timeouts with condition-based waiting, and use the included bisection script to find which test pollutes shared state. - Use Case: A CI pipeline fails intermittently. Instead of retrying fixes, instrument each layer (workflow, build script, signing), gather evidence showing where data breaks, form a single hypothesis, and verify with a failing test before fixing. ## Quick Start Use the systematic-debugging skill to investigate this failing test and find its root cause before suggesting any fix.