issue-fetcher

Fetch and analyze GitHub issues from the monorepo. Use when user asks about issues, what's blocking, issue status, dependencies, or wants to see issue details.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

The Issue Fetcher skill enables Claude to seamlessly retrieve and analyze GitHub issues within a monorepo environment. By automating the extraction of issue statuses, blockers, and dependencies, it streamlines technical project management and provides real-time visibility into development progress and milestone health.

Use Cases

  • Identifying Blockers: Automatically scan issue descriptions for 'depends on' or 'blocks' relationships to pinpoint critical bottlenecks in the development pipeline.
  • Sprint Progress Tracking: Generate instant summaries of open issues and task distribution for specific milestones to keep the team aligned on delivery goals.
  • Detailed Issue Retrieval: Quickly fetch comprehensive metadata for specific GitHub issues, including labels, assignees, and status, without leaving the chat interface.
  • Dependency Analysis: Map out complex task relationships by extracting and summarizing linked issues to understand the impact of specific technical debt or feature requests.
nameissue-fetcher
descriptionFetch and analyze GitHub issues from the monorepo. Use when user asks about issues, what's blocking, issue status, dependencies, or wants to see issue details.
allowed-toolsBash, Read, Grep, Glob

Issue Fetcher Skill

Purpose

Automatically fetch and summarize GitHub issues when the user asks about issue status, blockers, or dependencies. This is a read-only skill for information gathering.

When Claude Should Use This

  • User asks "show me issue #X"
  • User asks "what's blocking?"
  • User asks "what issues are open?"
  • User asks "what depends on this?"
  • User mentions issue numbers in context
  • User asks about sprint/milestone progress

Instructions

Fetch Single Issue

gh issue view <number> --json title,body,state,labels,milestone,assignees

List Issues

# All open issues
gh issue list --state open

# By milestone
gh issue list --milestone "OpenBadges Badge Generator"

# By label
gh issue list --label "type:feature"

Check Dependencies

Look for "depends on", "blocks", "after #X" in issue bodies:

gh issue view <number> --json body | jq -r '.body'

Output Format

Summarize findings clearly:

## Issue #X: <title>

**Status:** Open/Closed
**Labels:** label1, label2
**Milestone:** <milestone>

**Summary:** <1-2 sentence description>

**Dependencies:**

- Depends on: #Y, #Z
- Blocks: #A, #B

Repository Context

  • Owner: rollercoaster-dev
  • Repo: monorepo
  • Project Board: #11 "Monorepo Development"