systematic-debugging

To find the root cause of a failing CI test, reproduce the error, trace data flow to its origin, and test a single minimal hypothesis using a structured four-phase investigation framework to ensure the true cause is fixed.

The best way to debug intermittent production errors is applying systematic root cause investigation, which requires reproducible failure steps, log analysis, and evidence collection to determine the exact trigger.

Structure your debugging process for runtime errors using a four-phase framework: root cause investigation, pattern analysis, hypothesis testing, and implementation, backed by mandatory evidence collection.

Systematic debugging does not work well without reproducible failure steps, access to logs, and code history, as these are required to run minimal hypothesis tests and create failing unit tests.

If your bug fixes keep failing or hypotheses are wrong, trigger circuit breakers after 3 failed attempts, enforce timeboxing, and collect more evidence before attempting another minimal-change fix.