skills.rest
ebijun1007
ebijun1007COMMUNITY
Explore all skills by this author →
GitHub

issue-read

Aggregate parent, sub-issues, and related GitHub tickets into a structured report.

Updated Aug 23, 2026
Search Tags:#automation#github#issues#summary#read#sub-issues#parent-child
One-click install
npx skills add https://github.com/ebijun1007/vibe-coding --skill issue-read
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-read
Source: https://github.com/ebijun1007/vibe-coding/tree/main/.claude/skills/issue-read
Command: npx skills add https://github.com/ebijun1007/vibe-coding --skill issue-read

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently read GitHub issues by aggregating parent, sub-issues, and related tickets before summarizing, so you get a complete view without scattered references.

Core Features & Use Cases

  • Sub-issues aggregation: Prefers GitHub's official Sub-issues API to fetch child tickets and then retrieves full details for each.
  • Relationship-aware summarization: Parses the issue body to discover Parent, Sub-task, Child, and Related references and includes them in the final summary.
  • Activation by natural language: Responds to commands like "issue #NN を確認" or URLs to provide a consolidated report.

Quick Start

Ask me to read an issue, for example, 'Read issue #123', and I will fetch sub-issues and related tickets and present a consolidated summary.

Frequently Asked Questions about issue-read

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

FAQPage Schema
How do I read GitHub issues with sub-issues in one view?▼

To read GitHub issues with sub-issues in one view, this Skill aggregates parent and child tickets using the official Sub-issues API and outputs a consolidated, structured summary.

How does sub-issues aggregation work when summarizing GitHub issues?▼

Sub-issues aggregation works by fetching child tickets through GitHub's official Sub-issues API first, then falling back to parsing the issue body for Parent, Child, and Related references if needed.

Can I use issue URLs to fetch related tickets and sub-issues?▼

Yes, you can use issue URLs or issue numbers to activate the Skill, which retrieves full details via gh issue view and gh api to provide a consolidated report of related tickets.

What is the best way to summarize parent-child GitHub issues?▼

The best way to summarize parent-child GitHub issues is to aggregate related tickets, de-duplicate the results, and output a concise structured report that captures all relationship references in a single view.

Do I need the GitHub CLI to read and summarize sub-issues?▼

Yes, you need the GitHub CLI environment, as the Skill retrieves issue details directly through gh issue view and gh api commands to build its consolidated summary.

What happens if the GitHub Sub-issues API is not available?▼

If the Sub-issues API is not available, the Skill implements body-based fallbacks to parse the issue text for Parent, Sub-task, Child, and Related references and includes them in the final summary.

Related Skills

Explore More Software Engineering Skills→
drvossdrvoss
42

fix-github-issue

Resolve GitHub issues end-to-end from ticket to pull request.

Community
Intermediate
anyeloamtanyeloamt

gh-pr-issue-workflow

Automates GitHub issue and PR creation with sub-issue linking.

Community
Advanced
getty104getty104
4

post-scope-issue-body

Create GitHub Issues with parent-child and blocked-by dependencies from YAML input.

Community
Advanced
SpiceLabsHQSpiceLabsHQ

issue-tracker-github

Manage GitHub issues and projects using gh CLI commands.

Official
Advanced