Agent skill
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/issue-fetcher
SKILL.md
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"
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?