systematic-debugging

Root cause debugging prevents guess-and-check cycles by requiring evidence gathering, pattern comparison, and single-hypothesis testing before any fix is attempted. It traces failures backward through logs and stack traces to identify the original trigger.

Systematic debugging handles multi-component production incidents through a four-phase workflow: investigation, pattern analysis, hypothesis testing, and implementation. It applies pressure-resistant guardrails to prevent shortcut fixes when issues seem urgent.

Troubleshoot build issues without regressions by validating fixes with minimal tests and gathering evidence before implementation. When repeated attempts fail, an architectural review prevents regression risk and reduces wasted time.

Quick patches for unexpected production behavior fail because they bypass root-cause tracing. Without testing a single hypothesis and tracing the original trigger through call chains, the underlying failure remains unresolved and regression risk increases.

You need systematic bug analysis for test failures when quick patches are tempting, initial fixes do not work, or behavior is flaky. It enforces pressure-resistant guardrails to ensure root-cause-first investigation before any verified implementation.