skills.rest
benmatselby
benmatselbyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bms:github-issue-analyzer

Fetch GitHub issue details and generate a root-cause analysis with file references.

68|14|Updated Dec 21, 2017
Search Tags:#debugging#codebase#github#root-cause#gh-cli#issue-analysis
One-click install
npx skills add https://github.com/benmatselby/dotfiles --skill bms-github-issue-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bms:github-issue-analyzer
Source: https://github.com/benmatselby/dotfiles/tree/main/agents/skills/github-issue-analyzer
Command: npx skills add https://github.com/benmatselby/dotfiles --skill bms-github-issue-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes a GitHub issue to identify the underlying problem and provide concrete, actionable recommendations by correlating the issue with the relevant codebase and historical context.

Core Features & Use Cases

  • Fetch issue details (title, body, labels, state, and comments) using the gh CLI and extract structured information.
  • Inspect the repository codebase to locate implicated modules, configurations, and code paths related to the reported problem.
  • Produce a structured analysis including a summary, root-cause analysis with file references, relevant code, and concrete suggested fixes.

Quick Start

Provide a concise, structured issue analysis by fetching the issue from a URL and returning a root-cause and fix plan.

Frequently Asked Questions about bms:github-issue-analyzer

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 in my codebase?▼

To find the root cause of a GitHub issue, you can analyze the issue details and inspect the codebase to locate implicated modules. This process correlates issue metadata with code paths to generate a structured root-cause analysis with file references.

Can I use gh CLI to fetch issue details for code analysis?▼

Yes, you can use the gh CLI to fetch issue details. By running `gh issue view` with JSON output for title, body, labels, state, and comments, you extract structured data to analyze against your repository code.

What's the best way to turn GitHub issues into actionable fixes?▼

The best way to turn GitHub issues into actionable fixes is to fetch the issue context, explore the codebase for related configurations, and generate a structured report containing a concise summary, root-cause analysis, relevant code, and concrete suggested fixes.

How do I generate suggested fixes from GitHub issue comments?▼

You generate suggested fixes by extracting structured information from issue comments and correlating it with historical context. Inspecting the repository code paths allows you to produce concrete recommendations addressing the reported problem.

Does GitHub issue analysis work without local codebase access?▼

No, GitHub issue analysis requires local codebase access. Inspecting the repository to locate implicated modules and configurations is essential for producing a root-cause analysis with accurate file references.

Related Skills

Explore More Software Engineering Skills→
tomoasleeptomoasleep
2

read-github-issue

Fetch GitHub Issue details and download embedded images via gh-asset.

Community
Advanced
berkcangumusisikberkcangumusisik
11

debug-helper

Parse error messages and stack traces to identify root causes.

Community
Intermediate
shawndugganshawnduggan
31

nova-codebase

Generate a hierarchical map of Nova codebase modules and exports.

Community
Intermediate
cc01cccc01cc
4

bug-root-cause-structurer

Produces structured bug root-cause analyses with actionable repair plans and verification steps.

Community
Advanced