issue-analyze

Analyze GitHub issues to produce structured problem diagnoses and investigation plans.

187|24|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/sd0xdev/sd0x-dev-flow --skill issue-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-analyze
Source: https://github.com/sd0xdev/sd0x-dev-flow/tree/main/skills/issue-analyze
Command: npx skills add https://github.com/sd0xdev/sd0x-dev-flow --skill issue-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to diagnosing GitHub issues by reading issue details, classifying the problem, selecting an investigation strategy, and integrating four investigation tools to produce a consolidated report.

Core Features & Use Cases

  • Four-phase workflow: Read issue, classify problem, choose strategy, and execute investigations.
  • Unified investigation: Coordinates multiple tools (Read, Grep, Glob, Bash) to gather evidence and compose a findings report.
  • Use Case: When a bug report contains unclear symptoms, multiple labels, and conflicting reproduction steps, run this Skill to generate a root-cause analysis and suggested next steps.

Quick Start

Use the issue-analyze skill to assess a GitHub issue by running the command: /issue-analyze 123 and review the consolidated report.

Frequently Asked Questions about issue-analyze

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 with unclear reproduction steps?

Diagnosing a GitHub issue with unclear symptoms requires a structured investigation workflow that reads issue details, classifies the problem, and gathers evidence using multiple tools to pinpoint the root cause.

What is the best way to analyze a complex bug report across a repository?

Analyzing a complex bug report across a repository is best handled by a four-phase workflow: read the issue, classify the problem, execute an investigation using file search and shell tools, and consolidate the findings into a structured report.

How do I investigate a GitHub regression when the reported symptoms are conflicting?

Investigating a GitHub regression with conflicting symptoms involves classifying the issue type, selecting an appropriate investigation strategy, and coordinating multiple evidence-gathering tools to trace the root cause and document next steps.

Can I use command line tools to gather evidence for a GitHub issue investigation?

Yes, you can use command line tools to gather evidence for a GitHub issue investigation by integrating file reading, pattern searching, and shell commands within a unified workflow to collect relevant data and compose a findings report.

Does issue analysis work for bugs with multiple labels and complex repository structures?

Issue analysis works for bugs with multiple labels and complex repository structures by applying a four-phase workflow that reads and classifies the issue, then executes targeted investigations across the repository to generate a root-cause diagnosis.