skills.rest
dongg622
dongg622COMMUNITY
Explore all skills by this author →
GitHub

github-issue-rca

Diagnose GitHub issue root causes and generate Markdown reports.

Updated Aug 23, 2026
Search Tags:#root cause#GitHub#issue analysis#issue investigation#code repository#bug troubleshooting
One-click install
npx skills add https://github.com/dongg622/china-ai-chip-skill --skill github-issue-rca
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issue-rca
Source: https://github.com/dongg622/china-ai-chip-skill/tree/main/Ascend/github-issue-rca
Command: npx skills add https://github.com/dongg622/china-ai-chip-skill --skill github-issue-rca

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It automates the process of thoroughly analyzing GitHub issues to identify their potential root causes, reducing manual effort and increasing troubleshooting accuracy.

Core Features & Use Cases

  • Issue Content Collection: Extracts detailed information from a specified GitHub issue, including comments, labels, and affected components.
  • Similar Issue Search: Leverages multi-strategy searches based on error messages, symptoms, and file components to find related past issues.
  • Root Cause Hypothesis Generation: Analyzes code repositories, recent commits, and external resources to propose possible causes, complete with confidence levels.
  • Full Report Generation: Compiles an organized Markdown report with links to relevant issues, PRs, commits, files, and external references for comprehensive troubleshooting.

Quick Start

Provide the GitHub issue number or URL, and the system will retrieve details, search related issues, and generate an in-depth root cause analysis report automatically.

Frequently Asked Questions about github-issue-rca

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of a GitHub issue automatically?▼

To find the root cause of a GitHub issue automatically, provide the issue URL or number so the system can collect issue data, search related issues, analyze recent code changes, and generate a detailed troubleshooting report.

What is the best way to investigate bug regressions in a code repository?▼

The best way to investigate bug regressions in a code repository is to analyze recent commits and error patterns against the affected components, generating root cause hypotheses with confidence levels and relevant links.

How do I troubleshoot a GitHub issue when I don't know what changed?▼

To troubleshoot a GitHub issue with unknown changes, the system searches for similar past issues using error messages and file components, then analyzes recent commits to identify potential regressions and propose causes.

Can I use this issue analysis approach for any GitHub code repository?▼

Yes, you can use this issue analysis approach for any GitHub code repository by providing the specific issue number or URL to extract details, search historical issues, and compile a comprehensive markdown report.

Does GitHub issue investigation work without connecting external resources?▼

GitHub issue investigation works best when analyzing code repositories alongside external resources, ensuring thorough documentation by cross-referencing error patterns, known regressions, and relevant external links.

What does an automated root cause analysis report include?▼

An automated root cause analysis report includes extracted issue details, similar past issues, root cause hypotheses with confidence levels, and organized links to relevant PRs, commits, files, and external references.

Related Skills

Explore More Software Engineering Skills→
dyoshikawadyoshikawa
1

explain-issue

Analyze GitHub issue threads to extract problem statements and proposed technical solutions.

Community
Basic
RemseyMailjardRemseyMailjard

triage-issue

Investigate a reported bug and create a GitHub issue with a TDD fix plan.

Community
Intermediate
iimuziimuz
3

update-agents

Update AGENTS.md sections using git diff and commit history.

Community
Intermediate
artk0deartk0de
11

report-issue

Collect diagnostic data and verify duplicates before creating GitHub issues.

Community
Advanced