What problem does it solve?
Systematic Debugging eliminates guesswork and symptom-focused fixes by ensuring engineers find the root cause of bugs, test failures, and unexpected behavior before applying changes. It reduces repeated thrashing, prevents new regressions, and saves time by enforcing reproducible investigation and evidence-based fixes.
Core Features & Use Cases
- Four-phase workflow: mandatory Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation with clear stop conditions.
- Pressure-resistant rules: reproduce before fixing, form a single hypothesis, test minimally, create a failing test case, and stop to re-analyze if fixes fail repeatedly.
- Practical utilities and examples: guidance on tracing call stacks, defense-in-depth validation, condition-based waiting patterns, and a bisection script to find polluting tests.
- When to use: debugging flaky tests, production incidents, build and integration failures, and any multi-component system where the source of error is unclear.
Quick Start
Use the systematic-debugging skill to reproduce a failing test, gather cross-component evidence, form one clear hypothesis, and run the minimal change to verify the hypothesis.
