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.
When & Why to Use This Skill
The Issue Fetcher skill empowers Claude to interact directly with GitHub repositories to retrieve, analyze, and summarize issue data. It streamlines software project management by identifying blockers, checking dependency chains, and providing real-time status updates on milestones and labels within a monorepo environment. By automating the extraction of technical debt and task progress, it enhances developer productivity and team visibility.
Use Cases
- Blocker Identification: Automatically scan issue descriptions for 'depends on' or 'blocks' mentions to map out critical paths and resolve development bottlenecks.
- Sprint & Milestone Tracking: Generate comprehensive summaries of all open issues within a specific GitHub milestone to assess current velocity and remaining workload.
- Contextual Issue Deep-Dives: Instantly retrieve full details (labels, assignees, status) for specific issue IDs mentioned in chat to provide immediate context during technical planning.
- Dependency Mapping: Analyze the relationships between multiple issues to understand the sequence of feature implementation and cross-team dependencies.
| name | issue-fetcher |
|---|---|
| description | 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. |
| allowed-tools | Bash, 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"