answer-issue

Parse GitHub issues and deliver targeted analysis with actionable next steps.

Updated Nov 6, 2025
One-click install
npx skills add https://github.com/toumakido/my-claude --skill answer-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: answer-issue
Source: https://github.com/toumakido/my-claude/tree/main/skills/answer-issue
Command: npx skills add https://github.com/toumakido/my-claude --skill answer-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly understand and answer questions about GitHub issues by extracting reference data and providing concise, actionable conclusions.

Core Features & Use Cases

  • Structured issue analysis: Retrieve issue details (title, body, labels, comments) and summarize findings.
  • Context-driven responses: Answer prompts about root cause, related files, and suggested steps without making code changes.
  • Use Case: When an issue is opened by a workflow like /structure-issue or /restructure-issue, this Skill can rapidly provide an investigation report and next steps.

Quick Start

Provide the issue number and user prompt, e.g., "123 この問題の原因を調査して" to fetch and analyze issue 123.

Frequently Asked Questions about answer-issue

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

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

To investigate a GitHub issue root cause, provide the issue number and a prompt to fetch issue details, classify content as Bug or Feature, and deliver targeted analysis with actionable next steps.

Can I identify related files and reproduction steps from a GitHub issue?

Yes, you can identify related files and reproduction steps by parsing the GitHub issue, extracting reference data from the title, body, labels, and comments, and generating a concise investigation report.

Does GitHub issue analysis work with issues created by structure-issue workflows?

GitHub issue analysis works directly with issues created by structure-issue or restructure-issue workflows, rapidly parsing the structured content to provide context-driven responses about potential fixes.

What is the best way to analyze GitHub issues without making direct code changes?

The best way to analyze GitHub issues without code changes is to retrieve issue details and answer prompts about root cause and suggested steps, delivering a concise investigation report rather than modifying the repository.

How do I classify GitHub issues by type for a triage report?

To classify GitHub issues by type for a triage report, parse the issue content and categorize it as Bug, Feature, or Enhancement, then summarize findings with actionable next steps based on the classification.