agent-issue-investigator

Root cause analysis for a production incident involves systematically analyzing symptoms, documenting the environment, reproducing the issue, and collecting evidence to pinpoint the exact origin of the failure. This approach ensures thorough investigation before any fixes are attempted.

Investigating flaky test failures requires a systematic approach to trace the issue, gather necessary logs and evidence, and identify the fundamental cause rather than just treating the symptoms. Consistent reproduction is key to finding the origin.

Creating a reproducible bug report from an incomplete ticket involves transforming vague reports into precise analyses by documenting the environment, reproducing the issue consistently, and collecting supporting evidence to identify the root cause.

Debugging configuration errors is supported by meticulously tracing the issue and gathering all necessary logs and evidence to pinpoint the exact line of code or configuration that caused the failure.

A structured bug investigation output should detail the findings, including precise reproduction steps, the identified root cause, and acceptance criteria to ensure the issue is fully resolved.

A systematic approach to troubleshooting software bugs is needed when a critical bug is reported in production, ensuring thorough analysis, evidence collection, and root cause identification before fixes are attempted.