systematic-debugging

Systematic debugging isolates root causes by guiding error analysis, data flow tracing, and reproduction loop construction. This ensures the underlying issue is fully understood before any code is changed, preventing ineffective random patches.

The best way to debug failing test cases is applying a structured hypothesis-testing framework that uses minimal, single-variable probes to verify potential fixes. This scientific testing approach ensures accurate troubleshooting for software failures.

To troubleshoot performance regressions without random patches, enforce a disciplined, evidence-based investigation process. This involves isolating the root cause through data flow tracing and verifying fixes with single-variable probes before implementation.

You need terminal access for test execution and file system access for code analysis and instrumentation to run systematic debugging. These environment permissions allow the agent to build reproduction loops and trace data.

You should use a structured debugging process instead of guessing to prevent applying ineffective patches to software bugs. A rigorous methodology enforces evidence-based investigation, ensuring you identify and resolve actual root causes.