systematic-debugging

Systematic debugging is a structured workflow that enforces root-cause investigation before applying any code fixes. It identifies and resolves bugs by collecting evidence, analyzing patterns, and testing hypotheses to eliminate symptom-only fixes.

To debug test failures without regressions, follow a four-phase workflow: investigate the root cause, analyze patterns, test hypotheses, and implement the fix. You must create a failing test before fixing and validate each step to ensure stability.

Production error fixes often cause new issues because developers apply quick symptom-only patches instead of resolving the root cause. A systematic debugging approach mandates evidence collection and hypothesis testing before changes to prevent regressions.

You should use root-cause investigation whenever you encounter test failures, production crashes, performance regressions, or unexpected behavior. It stops you from applying quick fixes that mask the real problem and waste development time.

The best way to stop symptom fixes is to use a debugging skill that detects anti-patterns and mandates stopping when shortcuts appear. This enforces a disciplined workflow of evidence collection and verification before any implementation.

Yes, systematic debugging requires integrated testing by creating a failing test that reproduces the unexpected behavior before applying any fix. This validates the bug exists and confirms the resolution works without introducing regressions.