bug-reproduction-root-cause-hunter

To identify the root cause of a flaky test or vague bug report, normalize the report to collect expected behavior, errors, and environment details, then reproduce the failure using existing tests or logs to isolate the triggering conditions.

The best way to reproduce a production incident is to build a minimal repro plan using relevant logs, inputs, and environment states, narrowing the surface to the smallest set of files and conditions that trigger the issue.

To use diff analysis for investigating a regression, inspect recent code changes and related tests to test root-cause hypotheses, validating whether specific diffs triggered the observed failure.

Yes, after isolating a bug's failure conditions, you can generate a safe fix plan that proposes the smallest code change, a regression test, and rollout considerations to prevent future occurrences.

Yes, you need environment details, logs, and reproduction steps as inputs to accurately reproduce reported bugs and build a structured root-cause hypothesis for evidence-based fixes.