bug-root-cause-moderator

Root-cause analysis improvement takes critic feedback on your initial analysis, systematically addresses identified gaps, gathers supporting evidence, and reconstructs a more accurate causal chain with structured output including summary, execution trace, root cause location, code snippet, and confidence level.

A structured root-cause report requires a summary, execution trace, root cause file and line number, the problematic code, detailed explanation of why the bug occurred, why existing safeguards missed it, confidence assessment, and alternative hypotheses considered.

Root-cause analysis applies to software bug reports, execution traces, and code reviews. It systematically reconstructs the causal chain by integrating evidence from traces and code to identify where and why failures originated.

Critic feedback identifies missing data, logical gaps, and weak hypotheses in your initial analysis. Integration adds those missing elements, refines causal reasoning, and produces evidence-backed conclusions that withstand scrutiny.

Include alternative hypotheses when other potential causes could explain the symptoms but lack supporting evidence or contradict the execution trace. This demonstrates thorough analysis and justifies why the primary root cause is most likely.