github-issue-reader

Fetch and analyze GitHub issue details including comments, metadata, and discussion context. Use when user mentions issue numbers, URLs, or you need to understand implementation requirements from a GitHub issue.

⭐2stars🔀0forks📁View on GitHub🕐Updated Nov 25, 2025

When & Why to Use This Skill

The GitHub Issue Reader skill empowers Claude to fetch, analyze, and summarize GitHub issue data, including comments, metadata, and discussion history. By integrating directly with the GitHub CLI, it provides developers with instant technical context, implementation requirements, and decision-making history, significantly reducing the time spent manually navigating repository pages.

Use Cases

  • Extracting implementation requirements: Automatically parse issue descriptions to understand what needs to be built or fixed.
  • Summarizing long discussions: Synthesize key decisions and technical approaches from extensive comment threads to get up to speed quickly.
  • Context gathering via URLs: Provide a GitHub issue link to have the agent analyze the current status, labels, and assignees.
  • Identifying blockers: Scan issue metadata and comments to flag missing information, dependencies, or potential obstacles in a task.
  • Workflow automation: Use issue details to inform code generation or debugging tasks by ensuring the agent has the latest project context.
namegithub-issue-reader
descriptionFetch and analyze GitHub issue details including comments, metadata, and discussion context. Use when user mentions issue numbers, URLs, or you need to understand implementation requirements from a GitHub issue.

GitHub Issue Reader

Instructions

When to Invoke This Skill

  • User mentions a GitHub issue number (e.g., "issue #42", "#123")
  • User provides a GitHub issue URL
  • You need context about what needs to be implemented or fixed
  • Validating whether an issue has sufficient detail
  • Understanding discussion/decisions in issue comments

Standard Workflow

  1. Fetch Issue Details

    gh issue view <issue_number> --json title,body,state,labels,assignees,createdAt,updatedAt
    
  2. Fetch All Comments

    gh issue view <issue_number> --comments
    
  3. Analyze Content

    • Parse issue description for requirements
    • Review comments for implementation decisions
    • Identify any existing plans or approaches
    • Note any blockers or dependencies mentioned
  4. Synthesize Context

    • Summarize what needs to be done
    • Highlight key decisions from discussion
    • Flag any ambiguities or missing information
    • Note relevant links or references

Error Handling

If gh commands fail:

  • Check authentication: gh auth status
  • If not authenticated, guide user through: gh auth login
  • Verify issue number exists in the repository

If issue is closed:

  • Note the closed state
  • Check if there's a linked PR that resolved it
  • Determine if reopening is needed

Output Format

Provide structured summary:

Issue #<number>: <title>
Status: <open/closed>
Labels: <label list>

Summary:
<Brief description of what needs to be done>

Key Points from Discussion:
- <Important decision/context from comments>
- <Another key point>

Implementation Approach (if discussed):
<Any implementation details from comments>

Ambiguities/Questions:
- <Anything unclear that needs clarification>

Examples

Example 1: User mentions issue number

User: "Can you look at issue #42?"
Action: Run gh issue view 42 and gh issue view 42 --comments
Output: Structured summary of the issue

Example 2: Issue URL provided

User: "Check out https://github.com/owner/repo/issues/123"
Action: Extract issue number (123), fetch details
Output: Analysis of what the issue requires

Example 3: Vague reference

User: "What was that bug about the login form?"
Action: May need to search issues first (gh issue list --search "login form")
Output: Identify relevant issue(s) and provide context