investigate

To find the root cause of a bug, this Skill performs an in-depth investigation of errors and codebase logic without altering code. It leverages parallel subagents for comprehensive exploration and generates a markdown report detailing findings, root causes, and recommendations.

Yes, you can analyze a GitHub issue to understand a production error. The Skill handles GitHub issue inputs by fetching issue content directly for analysis, pinpointing the origin of errors and identifying the exact conditions that led to the failure.

The best way to investigate complex codebase modules without modifying code is using a read-only analytical approach. This Skill explores intricate system interactions and identifies test gaps, enabling root cause analysis and informed decision-making through a detailed markdown report.

Your existing tests fail to detect certain bugs due to unidentified test gaps. This Skill performs in-depth investigation to determine why existing tests failed to detect issues, analyzing faulty logic and exact failure conditions to pinpoint the origin of errors.

Yes, this investigation tool works with error tracebacks for debugging. You can investigate the error trace provided in the arguments to analyze the error traceback, understand the faulty logic, and identify the exact conditions that led to the critical bug.

To generate a markdown report for root cause analysis, provide an error trace or codebase question for investigation. The Skill performs comprehensive exploration using parallel subagents and outputs a markdown report detailing findings, root causes, and actionable recommendations.