investigate

Root-cause debugging prevents guessing by following a structured four-phase process: investigate, analyze, hypothesize, and implement. It orchestrates Bash, Grep, Read, and WebSearch to gather evidence and validate hypotheses before applying a fix.

Troubleshooting why something stopped working requires systematically gathering evidence across a project. A structured debugging workflow uses Glob to locate files, Read to inspect logic, and Grep to search for patterns, guiding you from initial investigation to a verified implementation.

Debugging an error through structured investigation involves four phases: investigate to gather context, analyze to examine evidence, hypothesize to identify the root cause, and implement to apply the fix. It coordinates shell commands and file search tools to validate each step deterministically.

Yes, root-cause analysis can automate evidence gathering using Bash and Grep. The debugging workflow orchestrates these tools alongside Read, Write, Edit, Glob, and WebSearch to execute deterministic tasks, search codebases, and collect the necessary proof to validate hypotheses.

Use a phased debugging approach when you need to understand why an error occurred and prevent regressions. Directly editing code risks guessing; the four-phase process of investigating, analyzing, hypothesizing, and implementing ensures you validate root causes with evidence before making changes.