systematic-debugging

Root-cause debugging is a disciplined, phase-driven approach to identify the underlying causes of bugs before applying fixes. It stops guesswork by enforcing structured evidence gathering, pattern analysis, and hypothesis testing to ensure thorough analysis and reduce rework.

To debug production issues or test failures systematically, follow a four-phase workflow: investigate root causes, analyze patterns, test hypotheses, and implement fixes. Use integrated tools like read_file, search_files, and terminal to read errors, reproduce issues, and trace data flow.

Yes, this systematic debugging approach is applicable to performance problems and integration bugs. It prescribes structured evidence gathering and regression safety across diverse scenarios, ensuring thorough diagnosis and reliable fixes for complex multi-component software issues.

The best way to handle multi-component debugging is using the delegate-task feature for collaborative investigations. It allows you to distribute debugging tasks across different components while maintaining the four-phase root-cause workflow and integrating with available tooling.

Phase-based hypothesis testing utilizes integrated tools including read_file, search_files, terminal, and web_search. These tools allow you to gather evidence, reproduce errors, and validate your hypotheses during the debugging workflow without requiring external dependencies.