What problem does it solve? Developers under time pressure often apply quick symptom fixes that fail repeatedly, causing hours of guess-and-check thrashing. This Skill enforces a disciplined four-phase debugging methodology that finds the actual root cause before any fix is attempted. ## 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 (backward call-stack tracing), defense-in-depth validation at four layers, and condition-based waiting to replace flaky arbitrary timeouts in tests. - Bisection Script: A find-polluter.sh script that runs tests one-by-one to identify which test creates unwanted files or state. - Use Case: When a test fails intermittently or a production bug resists multiple fix attempts, load this Skill to systematically trace the failure to its source, form a single testable hypothesis, and implement one verified fix. ## Quick Start Use the systematic-debugging skill to investigate this failing test and find its root cause before suggesting any fix.
