Skill

gh-fetch-issue

Fetches GitHub issues with attachments (images, screenshots) downloaded locally for Claude to read. Proactive for user-provided URLs, issue reads/checks, number references, or screenshot queries.

Github

Git

git-workflow

npx claudepluginhub takazudo/claude-resources

Configuration

Arguments: <issue-url-or-number> [--repo owner/repo]

Tool Access

This skill is limited to using the following tools:

Bash(bash $HOME/.claude/skills/gh-fetch-issue/scripts/fetch-issue.sh *)ReadGlob

Preview

Fetch a GitHub issue with attachments downloaded locally for Claude to read.

Supporting Assets

scripts/fetch-issue.sh

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars7

Forks0

Last CommitMay 7, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

gh-fetch-issue

Fetch a GitHub issue with attachments downloaded locally for Claude to read.

Why This Skill Exists

GitHub issue images (github.com/user-attachments/assets/...) require authentication and cannot be fetched via WebFetch. This skill downloads everything locally so Claude can read both the markdown content and all attached images.

Usage

# By URL bash $HOME/.claude/skills/gh-fetch-issue/scripts/fetch-issue.sh https://github.com/owner/repo/issues/123 # By issue number (auto-detects repo from current git remote) bash $HOME/.claude/skills/gh-fetch-issue/scripts/fetch-issue.sh 123 # By issue number with explicit repo bash $HOME/.claude/skills/gh-fetch-issue/scripts/fetch-issue.sh 123 --repo owner/repo

Workflow

Run the fetch script — it prints the output directory path

Read {output-dir}/issue.md for the issue content

If an assets/ subdirectory exists, read the image files to see screenshots and attachments

Present findings to the user

Output Location

$HOME/cclogs/{repo-slug}/{date}-issue-{number}/ ├── issue.md # Issue content with local image paths └── assets/ # Downloaded images (if any) ├── body-{id}.png └── comment-0-{id}.png

The {repo-slug} is owner-repo in lowercase (e.g., zudolab-zudo-text). The {date} is YYYYMMDD.

gh-fetch-issue

Fetch a GitHub issue with attachments downloaded locally for Claude to read.

Why This Skill Exists

Usage

# By URL
bash $HOME/.claude/skills/gh-fetch-issue/scripts/fetch-issue.sh https://github.com/owner/repo/issues/123

# By issue number (auto-detects repo from current git remote)
bash $HOME/.claude/skills/gh-fetch-issue/scripts/fetch-issue.sh 123

# By issue number with explicit repo
bash $HOME/.claude/skills/gh-fetch-issue/scripts/fetch-issue.sh 123 --repo owner/repo

Workflow

Run the fetch script — it prints the output directory path
Read {output-dir}/issue.md for the issue content
If an assets/ subdirectory exists, read the image files to see screenshots and attachments
Present findings to the user

Output Location

$HOME/cclogs/{repo-slug}/{date}-issue-{number}/
├── issue.md          # Issue content with local image paths
└── assets/           # Downloaded images (if any)
    ├── body-{id}.png
    └── comment-0-{id}.png

The {repo-slug} is owner-repo in lowercase (e.g., zudolab-zudo-text). The {date} is YYYYMMDD.