bug-root-cause-critic

Root cause analysis critique evaluates whether the investigation accurately explains bug behavior by assessing evidence quality, hypothesis correctness, and consideration of alternative explanations. Provide your analysis report to receive structured scoring and improvement recommendations.

Evidence-based root cause analyses require traceable references, concrete code lines, reproducible steps, and clear linkage between symptoms and the identified cause. The critique identifies gaps in evidence, unsupported claims, and missing alternatives to strengthen your investigation.

Yes. Root cause analysis critique applies to software bug investigations, incident postmortems, and code-review reports, ensuring your post-incident analysis identifies the true cause rather than symptoms and validates hypotheses against collected evidence.

The critique evaluates whether your hypothesis logically follows from evidence, considers competing explanations, and addresses why the bug occurred at a specific point in the codebase. It flags unsupported leaps and suggests concrete evidence to validate or refute your hypothesis.

Include bug behavior description, evidence references (logs, traces, code lines), reproduction steps, your hypothesis explaining the cause, and any alternative explanations you considered. The more concrete and traceable your analysis, the more actionable the critique.