diagnose

A structured debugging approach systematically isolates code bugs through a six-step loop: reproduce, minimise, hypothesise, instrument, fix, and regression-test. This method builds a deterministic feedback loop to rigorously verify the root cause before applying changes.

To build a feedback loop for bug fixing, you create a fast, deterministic, agent-runnable pass/fail signal. This ensures consistent bug reproducibility, allowing you to test falsifiable hypotheses and confirm fixes through targeted instrumentation.

The best way to hypothesize bug causes is to minimize the reproduction case and formulate falsifiable predictions. By instrumenting the code with targeted logging, you can test these hypotheses directly against a deterministic pass/fail signal.

Yes, a structured bug diagnosis process requires a clear understanding of the codebase and debugging techniques. You need this foundational knowledge to effectively reproduce bugs, minimize variables, and build a reliable feedback loop.

To perform regression testing after a bug fix, you run the deterministic pass/fail signal established during the feedback loop construction. This confirms the fix resolves the issue without introducing new code quality problems.

You should avoid a structured debugging approach if you lack a clear understanding of the codebase or the ability to create a deterministic reproduction case. Without a reproducible signal, the hypothesis testing and instrumentation steps cannot function effectively.