GitHub Issue Root Cause Analysis

This skill provides a systematic approach to analyzing GitHub issues and identifying their possible root causes, with emphasis on searching similar issues first and collecting all relevant links.

Output Requirement

After completing any analysis, you MUST save the report to a markdown file:

• File name: {issue_number}_rca.md (e.g., 123_rca.md for issue #123)
• Location: Current working directory
• Tool: Use write tool to create/update the file
• If file doesn't exist: Create it directly with write
• If file exists: read it first, then overwrite with new content

The analysis is considered incomplete until the report file is saved.

When to Use This Skill