investigate-bug

To investigate a GitHub issue for root cause, you fetch issue data via gh, extract error messages and reproduction steps, trace code paths, and generate a structured investigation report posted back to the issue.

Mapping code paths affected by a bug involves reading involved files, tracing call paths, and mapping error propagation to pinpoint the root cause, which produces a structured investigation report for the GitHub issue.

Yes, you can automatically post an investigation report to a GitHub issue. The process reads issue data via gh, analyzes the code paths, and generates a structured report directly back to the GitHub issue thread.

Yes, you need the gh CLI to extract error messages. Reading issue data via gh is required to fetch and validate issue details, extract reproduction steps, and identify affected files for the investigation.

A bug investigation report includes the identified root cause, affected files, scope of the issue, mapped code paths, and extracted error messages, providing a structured document posted directly to the GitHub issue.

Tracing error propagation to identify affected files requires reading involved files and mapping the call paths from the extracted error messages, ultimately documenting the root cause and scope in an investigation report.