What problem does it solve?
Systematic Debugging eliminates guesswork when diagnosing software failures by forcing a disciplined, evidence-first approach that prevents symptom-only fixes and repeated regressions. It helps engineers avoid time-wasting shotgun fixes and makes debugging faster and more reliable under both calm and high-pressure conditions.
Core Features & Use Cases
- Four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation with failing tests.
- Multi-component tracing & instrumentation: Practical guidance for adding diagnostics across component boundaries to locate the failing layer.
- Pressure-resistant rules: Explicit anti-patterns and stop-gates ("ALWAYS", "NEVER", single-hypothesis rule) to avoid shortcuts during emergencies.
- Supporting techniques: Defense-in-depth validation, condition-based waiting, root-cause tracing, and a small bisection shell helper for test pollution detection.
- Use Case: Reproduce a flaky CI failure, trace the bad value to its origin, form a minimal hypothesis, add a failing test, and implement a single verified fix.
Quick Start
Use systematic-debugging to run the four-phase process: reproduce the issue, gather evidence across components, form a single hypothesis and test it minimally, then create a failing test and implement the root-cause fix.
