investigate

To find the root cause of a bug, you need a structured debugging workflow that gathers evidence using tools like Bash, Read, and Grep before attempting any fixes. This approach enforces a four-phase investigation to verify the underlying issue.

The best way to debug unexpected errors without guessing is to follow a disciplined root-cause analysis process. This involves investigating, analyzing, hypothesizing, and implementing, ensuring no code fixes are applied until the root cause is verified.

Yes, you can use a structured investigation to troubleshoot failing systems by applying a four-phase root-cause analysis. It guides you through evidence gathering with tools like WebSearch and Glob to identify why a system stopped working.

You should use a root-cause analysis workflow when you report errors, experience unexpected behavior, or need to investigate why a software system is broken. It provides proactive guidance and suggests potential causes for complex issues.

Yes, this debugging approach supports searching for external solutions by integrating WebSearch alongside file reading and editing tools. This allows you to gather evidence and explore potential fixes during the hypothesis phase.