investigate

Hypothesis-driven debugging prevents recurring bugs by requiring evidence collection and root-cause verification before applying fixes. It enforces a phase-based workflow encompassing investigation, pattern analysis, hypothesis testing, implementation, and verification.

Structured debugging workflows prevent fix-quick firefighting by requiring evidence-based investigations and explicit root-cause verification steps before changes. This enforces traceability and ensures durable solutions across complex systems.

Start root-cause investigation by collecting symptoms and reading the code path to identify the root cause. Use guided tool-assisted analysis with commands to collect evidence and reproduce issues before forming testable hypotheses.

Hypothesis-driven debugging integrates with tools like ask_user and bash to facilitate guided tool-assisted analysis. This integration prompts engineers to collect evidence, reproduce issues, and validate fixes during the investigation.

Applying pattern analysis without explicit root-cause verification risks implementing superficial fixes that fail to address the actual issue. A documented verification workflow, including a regression test, is required to ensure the fix is durable and safe.