skills.rest
yoshisada
yoshisadaCOMMUNITY
Explore all skills by this author →
GitHub

issue

Analyze GitHub issues and generate concrete repository improvement plans.

Updated Mar 26, 2026
Search Tags:#github#issues#code-review#analyze#project-management#change-proposal
One-click install
npx skills add https://github.com/yoshisada/ai-repo-template --skill issue-yoshisada
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/yoshisada/ai-repo-template/tree/main/.claude/skills/issue
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill issue-yoshisada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read a GitHub issue and analyze how the repo can be improved. Proposes concrete changes to skills, hooks, templates, agents, or the plugin structure. Use as "/issue 42" or "/issue https://github.com/yoshisada/ai-repo-template/issues/42".

Core Features & Use Cases

  • Read and interpret issue titles, bodies, and comments to identify problems and feature requests.
  • Map suggested changes to repository components (skills, hooks, templates, agents, plugin structure) and generate concrete plans.
  • Provide actionable guidance that can be reviewed, refined, and implemented by maintainers.

Quick Start

Provide the issue reference (number or URL) and let the skill generate an improvement plan.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I analyze GitHub issues to propose concrete repository improvements?▼

Analyzing GitHub issues involves parsing issue titles, bodies, and comments to identify problems, classifying impact across plugin areas, and generating a compact change plan with specific file paths for repository improvements.

Can I use an issue URL or issue number to generate a change proposal for my project?▼

Yes, you can supply an issue URL or a numeric issue reference like "/issue 42" to automatically extract issue context and generate an actionable change proposal for your repository.

What is the best way to map feature requests from issues to repository components?▼

Mapping feature requests requires interpreting issue content and classifying the suggested changes against repository components like skills, hooks, templates, agents, and the overall plugin structure to generate concrete plans.

Does this issue analysis approach work for internal projects as well as open-source repositories?▼

Yes, this issue analysis approach applies to both open-source and internal projects, automating problem identification and change proposal generation across various repository structures.

How do I get actionable guidance from GitHub issue comments for project management?▼

Actionable guidance is produced by parsing issue comments and titles to identify core problems, then mapping those findings to a compact change plan that maintainers can review, refine, and implement.

What kind of output should I expect when automating GitHub issue analysis?▼

Automating GitHub issue analysis yields a compact change plan that includes proposed modifications mapped to specific file paths, covering skills, hooks, templates, agents, or plugin structures.

Related Skills

Explore More Software Engineering Skills→
theZMCtheZMC
2

read-github-issue

Read GitHub issue status, metadata, and comments via gh CLI.

Community
Intermediate
TeamSPWKTeamSPWK
2

evolution

Orchestrate scanners, filters, proposals, and gate chains for Nova self-evolution.

Official
Advanced
primeBeriprimeBeri
1

Radberi-PlanExecute

Automate management, verification, and review of project implementation plans.

Community
Advanced
baekenoughbaekenough
13

professor-triage

Analyze GitHub issues against the codebase and post prioritized triage comments.

Community
Advanced