hunt

To find the root cause of a failing test, formulate a one-sentence testable hypothesis citing specific files or lines, then use targeted instrumentation like log lines or minimal tests to gather evidence before making code changes.

The best way to debug unexpected crashes during incident triage is to validate hypotheses with concrete evidence, enforce environment verification, and avoid random code changes to prevent symptom-only patches and regression cascades.

To stop making random code changes when diagnosing errors, enforce a three-failed-hypotheses stop limit with user escalation, and require grep-before-edit checks to validate assumptions against the actual codebase.

Yes, you can use an evidence-based approach for continuous integration failures by tracing execution paths, proposing a single targeted instrument to confirm hypotheses, and producing a minimal, testable fix plan.

You should verify your environment before debugging runtime crashes to ensure the issue is reproducible and isolated, preventing wasted effort on environment-specific discrepancies rather than true code defects.

Evidence-based debugging works for local development and production incidents by applying consistent safety rules like grep-before-edit and hypothesis validation to trace execution paths and gather concrete proof.