What problem does it solve? Random fixes and quick patches waste time, mask underlying issues, and introduce new bugs. This Skill enforces a disciplined debugging methodology that finds the actual root cause before any fix is attempted, even under time pressure or social pressure to apply a quick workaround. ## Core Features & Use Cases - Four-Phase Process: Root cause investigation, pattern analysis, hypothesis testing, and implementation, with mandatory completion of each phase before proceeding. - Supporting Techniques: Includes root cause tracing through call stacks, defense-in-depth validation at multiple layers, condition-based waiting to replace flaky timeouts, and a bisection script to find test polluters. - Pressure Resistance: Explicit anti-patterns, red flags, and rationalization tables that stop shortcut fixes during emergencies, exhaustion, or authority pressure. - Use Case: When a production test fails intermittently, follow Phase 1 to reproduce and gather evidence, trace the bad value to its source, form a single hypothesis, and implement one verified fix instead of stacking arbitrary sleep timeouts. ## Quick Start Ask the AI to debug a failing test or bug using the systematic-debugging skill and require root cause investigation before any fix is proposed.
