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 systematic debugging process 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. - Defense-in-Depth Validation: Add validation at entry, business logic, environment, and debug layers so the bug becomes structurally impossible. - Condition-Based Waiting: Replace arbitrary timeouts in flaky tests with condition polling to eliminate race conditions. - Use Case: A test fails in CI but passes locally. Instead of tweaking timeouts, follow Phase 1 to gather evidence at each component boundary, trace the bad value to its source, write a failing test that reproduces it, then fix the root cause and verify red-green. ## Quick Start Use the investigating-bugs skill to find the root cause of this failing test before proposing any fix.
