systematic-debugging

Root cause debugging systematically investigates why a failure occurs by analyzing error messages, reproducing the issue consistently, and gathering evidence before proposing fixes. This four-phase framework—investigation, pattern analysis, hypothesis testing, and implementation—ensures you address underlying causes rather than surface symptoms, preventing recurring bugs.

Systematic debugging guides you through careful error analysis, consistent reproduction across components, and evidence comparison with working references. It enforces completing root-cause investigation first, then pattern analysis to identify key differences and dependencies before forming and testing a single, minimal hypothesis.

Performance and integration problems require phase-specific investigation: gather reproducible evidence, compare broken code against working examples, form a testable hypothesis, then make minimal changes to verify it. This workflow prevents wasted fixes and ensures the underlying cause is resolved, not just the visible symptom.

Addressing symptoms without understanding root causes creates technical debt and cascading failures. Systematic debugging enforces anti-shortcut rules and phase-specific checklists that require thorough investigation and minimal, hypothesis-driven changes, ensuring fixes are repeatable and lasting.

Yes. Systematic debugging covers test failures, production bugs, performance issues, and integration problems through a unified four-phase framework. Phase 1 completion is mandatory before proposing fixes, ensuring consistent, root-cause-driven investigation across all failure types.