investigate

Structured root-cause debugging is a repeatable investigation workflow that enforces collecting symptoms, reproducing the bug, hypothesizing, and implementing fixes to find the actual source of errors before applying changes.

Debug a software crash by following a four-phase workflow: investigate symptoms, analyze logs and reproduce the bug, hypothesize the root cause, and implement fixes using Bash, Grep, Read, and Edit tools.

Yes, this structured debugging workflow applies to errors, crashes, performance slowdowns, and unexpected behavior across local and remote environments by orchestrating Bash, Grep, Glob, Read, and WebSearch tools.

The best way to reproduce a bug is using a structured investigation approach that collects symptoms and logs first, then uses Bash and Grep to recreate the exact conditions, ensuring you find the root cause before fixing.

No external dependencies or components are required. This root-cause debugging workflow orchestrates standard tools including Bash, Read, Write, Edit, Grep, Glob, AskUserQuestion, and WebSearch to perform the investigation.

Avoid a structured root-cause investigation workflow when dealing with trivial syntax errors or obvious one-line fixes, as the four-phase process of collecting symptoms and hypothesizing adds overhead better suited for complex regressions.