investigate

Root-cause debugging uses a structured, phase-based workflow to identify actual causes rather than symptoms. You collect symptoms, trace code paths, and form testable hypotheses before implementing fixes, ensuring reproducible validation across the codebase.

A structured debugging workflow applies phases like investigation, analysis, hypothesis testing, implementation, and verification. It uses tooling such as grep, read, and write to gather evidence and validate fixes deterministically across the software.

To reproduce and validate bugs deterministically, create reproducible steps within a phase-based investigation workflow. Use tooling like grep and read to trace code paths, test hypotheses, and confirm fixes before generating a structured debug report.

Yes, tool-guided investigation uses grep, read, write, and edit to collect evidence and trace code paths. These tools help form testable hypotheses and validate findings across the codebase during root-cause analysis.

A structured debug report should include collected evidence, the identified root cause, fix implementation details, and a telemetry log of the debugging session. This ensures reproducibility and validates the verification phase outcomes.