skills.rest
luongnv89
luongnv89COMMUNITY
Explore all skills by this author →
Website𝕏@luongnv89GitHub

issue-analysis

Analyze a GitHub issue to identify root cause, affected files, and implementation options.

3|Updated Mar 20, 2026
Search Tags:#github#triage#code-review#root-cause#issue-analysis#analysis-pipeline
One-click install
npx skills add https://github.com/luongnv89/idd --skill issue-analysis-luongnv89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-analysis
Source: https://github.com/luongnv89/idd/tree/main/src/skills/issue-analysis
Command: npx skills add https://github.com/luongnv89/idd --skill issue-analysis-luongnv89

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill analyzes a GitHub issue to identify root cause, affected files, architectural implications, and actionable performance options, generating a durable, structured understanding for downstream decisions.

Core Features & Use Cases

  • Extract issue context (title, body, labels) and map findings to code changes and dependencies.
  • Scan the repository codebase and history to surface root cause, affected modules, and viable implementation options.
  • Score complexity and risk, present a recommended approach, and persist a JSON analysis to .gitissue/analysis-N.json for future reference.

Quick Start

Invoke /issue-analysis N to perform a full analysis of issue #N and review the resulting JSON at .gitissue/analysis-N.json.

Frequently Asked Questions about issue-analysis

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

FAQPage Schema
How do I analyze a GitHub issue to find its root cause and affected files?▼

To analyze a GitHub issue for root cause and affected files, use issue-analysis to scan the repository codebase and history. It maps the issue context to code changes, scores complexity and risk, and presents viable implementation options.

What is the best way to turn GitHub issues into structured work orders for my team?▼

Turning GitHub issues into structured work orders involves extracting issue context and scanning repository history to surface architectural implications. This process scores complexity and risk, producing a durable JSON analysis for actionable performance options.

How do I perform a root-cause analysis on a GitHub issue and save the results?▼

Perform a root-cause analysis on a GitHub issue by invoking the analysis pipeline against repository context. The results are persisted to .gitissue/analysis-N.json, containing a git_state and decision_record for future reference and downstream integration.

Can I use issue analysis to score complexity and risk for code review?▼

Yes, you can use issue analysis to score complexity and risk for code review. It identifies viable implementation options and architectural implications, generating a structured report that helps evaluate the impact of proposed code changes.

Does the issue triage process require external dependencies to map findings to code changes?▼

No external dependencies are required for the issue triage process. The analysis pipeline operates directly against the repository context to extract issue context and map findings to code changes, dependencies, and affected modules.

Related Skills

Explore More Software Engineering Skills→
greenheadHQgreenheadHQ
4

create-issue

Create structured GitHub issues with auto-enriched labels and duplicate checks.

Community
Intermediate
openwopopenwop
1

pr

Create structured pull requests for the openwop repository with compliance checks.

Official
Intermediate
BerryKuipersBerryKuipers
7

parse-ai-analysis

Parse GitHub AI analysis comments into structured JSON sections.

Community
Intermediate
softsparksoftspark
161

triage-issue

Investigate reported bugs and produce root-cause analyses with TDD fix plans.

Community
Advanced