Ask Navigator
Yeachan-Heo/oh-my-claudecode
Charts a foggy effort into a map of decision tickets on the repo's issue tracker and works through them one per session, producing decisions rather than deliverables.
Pulls a GitHub issue's description, comments, labels, assignees, milestone and linked pull requests into one markdown report so the agent can plan a fix.
Install GitHub Issue Reader
$ npx skills add jumppad-labs/jumppad --skill github-issue-reader -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jumppad-labs/jumppad github-issue-reader --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jumppad-labs/jumppad.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/github-issue-reader .claude/skills/github-issue-reader && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "github-issue-reader" agent skill from https://github.com/jumppad-labs/jumppad/tree/main/.claude/skills/github-issue-reader into .claude/skills/github-issue-reader/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-reader", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jumppad-labs/jumppad/tree/main/.claude/skills/github-issue-readerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jumppad-labs/jumppad --skill github-issue-reader -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jumppad-labs/jumppad github-issue-reader --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jumppad-labs/jumppad.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/github-issue-reader .agents/skills/github-issue-reader && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "github-issue-reader" agent skill from https://github.com/jumppad-labs/jumppad/tree/main/.claude/skills/github-issue-reader into .agents/skills/github-issue-reader/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-reader", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jumppad-labs/jumppad --skill github-issue-reader -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jumppad-labs/jumppad github-issue-reader --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jumppad-labs/jumppad.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/github-issue-reader .cursor/skills/github-issue-reader && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "github-issue-reader" agent skill from https://github.com/jumppad-labs/jumppad/tree/main/.claude/skills/github-issue-reader into .cursor/skills/github-issue-reader/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-reader", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jumppad-labs/jumppad.git --path .claude/skills/github-issue-reader--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jumppad-labs/jumppad --skill github-issue-reader -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jumppad-labs/jumppad github-issue-reader --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jumppad-labs/jumppad.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/github-issue-reader .gemini/skills/github-issue-reader && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "github-issue-reader" agent skill from https://github.com/jumppad-labs/jumppad/tree/main/.claude/skills/github-issue-reader into .gemini/skills/github-issue-reader/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-reader", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jumppad-labs/jumppad github-issue-readerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jumppad-labs/jumppad --skill github-issue-reader -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jumppad-labs/jumppad.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/github-issue-reader .github/skills/github-issue-reader && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "github-issue-reader" agent skill from https://github.com/jumppad-labs/jumppad/tree/main/.claude/skills/github-issue-reader into .github/skills/github-issue-reader/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-reader", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jumppad-labs/jumppad --skill github-issue-reader -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jumppad-labs/jumppad github-issue-reader --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jumppad-labs/jumppad.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/github-issue-reader .opencode/skills/github-issue-reader && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "github-issue-reader" agent skill from https://github.com/jumppad-labs/jumppad/tree/main/.claude/skills/github-issue-reader into .opencode/skills/github-issue-reader/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issue-reader", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
github-issue-reader- GitHub stars
- 263
- Token cost
- ~958 tokens
- SKILL.md length
- 347 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MPL-2.0
At a glance
Pulls a GitHub issue's description, comments, labels, assignees, milestone and linked pull requests into one markdown report so the agent can plan a fix.
- Works in 3 steps: Issue number (for current repository): 123 → Owner/repo format: owner/repo#123 → Full URL:…
- Planning a fix for a specific GitHub issue
- SKILL.md covers Overview, When to Use This Skill, Quick Start and Usage Instructions, plus 1 more section
- Runs Python scripts from its folder; calls gh; reaches github.com
What it does
This skill runs a bundled Python script, fetch_issue.py, that collects everything attached to a GitHub issue and prints it as formatted markdown. The report covers the title, URL, open or closed state, author, timestamps, labels, assignees, milestone, the full description and every comment with its author and time.
You can point it at an issue in three ways: a bare number for the current repository, an owner/repo#number reference, or a full issue URL. It also lists cross-referenced issues and linked pull requests, so the agent sees existing work before it writes a plan. The GitHub CLI (gh) has to be installed and logged in, and the script reports a missing install, a missing login or an unknown issue.
When your agent uses it
- Planning a fix for a specific GitHub issue
- Gathering requirements from an issue thread before coding starts
- Checking which pull requests are already linked to an issue
- Reviewing the history and discussion of a long-running issue
Example prompts
- “Read issue 123 and draft an implementation plan for it.”
- “Summarize https://github.com/owner/repo/issues/123 including every comment and any linked PRs.”
- “Before we start, load the full context of owner/repo#123 so we know what was already tried.”
Requirements
- GitHub CLI (gh), installed and authenticated
- Python to run scripts/fetch_issue.py
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Issue number (for current repository): 123
- Owner/repo format: owner/repo#123
- Full URL: https://github.com/owner/repo/issues/123
What it can do on your machine
Read from SKILL.md and the folder at commit 34289ff. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
Also links to:
cli.github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
GitHub Issue Reader loads about 958 tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 347 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from jumppad-labs/jumppad at commit 34289ff, republished under its MPL-2.0 licence (© jumppad-labs). 347 words, ~958 tokens.
Download SKILL.mdSave it as
.claude/skills/github-issue-reader/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- github-issue-reader
- description
- Load comprehensive GitHub issue information including title, description, comments, labels, assignees, milestones, and related items (linked PRs and cross-references). This skill should be used when planning to fix an issue, when detailed issue context is needed for implementation work, or when a plan command needs to understand the full scope of an issue.
GitHub Issue Reader
Overview
Fetch complete GitHub issue information to provide context for planning and implementation. This skill retrieves all relevant data from a GitHub issue including the description, all comments and discussion, metadata (labels, assignees, milestones), and related items (linked pull requests and cross-referenced issues).
When to Use This Skill
Use this skill when:
- Creating a plan to fix or implement an issue
- Understanding the full context and discussion around an issue
- Gathering requirements from an issue before starting work
- Reviewing an issue's history and related work
- Analyzing cross-references and linked pull requests
Quick Start
Fetch issue information using the fetch_issue.py script with any of these formats:
# Current repository issue by number
scripts/fetch_issue.py 123
# Specific repository issue
scripts/fetch_issue.py owner/repo#456
# Issue by full URL
scripts/fetch_issue.py https://github.com/owner/repo/issues/789The script outputs formatted markdown containing all issue information.
Usage Instructions
Prerequisites
Ensure the GitHub CLI (gh) is installed and authenticated:
gh auth statusIf not authenticated, run:
gh auth loginFetching Issue Information
Execute the fetch_issue.py script with an issue reference. The script accepts three formats:
- Issue number (for current repository):
123 - Owner/repo format:
owner/repo#123 - Full URL:
https://github.com/owner/repo/issues/123
The script will fetch and output:
- Issue number, title, and URL
- Current state (open/closed)
- Author and timestamps (created, updated, closed)
- Labels, assignees, and milestone
- Full issue description
- All comments with authors and timestamps
- Cross-referenced issues
- Linked pull requests
Example Output Structure
# Issue #123: Add new feature for X
**URL**: https://github.com/owner/repo/issues/123
**State**: open
**Author**: username
**Created**: 2024-10-15T10:30:00Z
**Labels**: enhancement, priority-high
**Assignees**: developer1, developer2
## Description
[Full issue description]
## Comments (3)
### Comment 1 by user1 (2024-10-16T09:00:00Z)
[Comment body]
## Linked Pull Requests
- PR #124 - Fix for issue #123
## Cross-Referenced Issues
- #120 - Related issueIntegration with Planning Workflows
When using this skill as part of a planning workflow:
- Invoke the skill with the issue reference
- Review the complete issue context provided
- Use the information to create an accurate implementation plan
- Reference specific comments or requirements from the issue
- Check linked PRs for existing work or context
Error Handling
The script handles common errors:
- gh CLI not found: Install GitHub CLI from https://cli.github.com
- Not authenticated: Run
gh auth login - Issue not found: Verify the issue number and repository
- Rate limiting: Wait and retry, or check GitHub API rate limits
Resources
scripts/fetch_issue.py
Python script that uses the GitHub CLI to fetch comprehensive issue data. Can be executed directly without loading into context.
Usage: scripts/fetch_issue.py <issue-reference>
Returns: Formatted markdown with complete issue information
Requirements:
- GitHub CLI (
gh) installed and authenticated - Python 3.6+
- Internet connection
© jumppad-labs, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in .claude/skills/github-issue-reader of jumppad-labs/jumppad.
- SKILL.md
- scripts/fetch_issue.py
Open the folder on GitHubat commit 34289ff
Compare with similar skills
GitHub Issue Reader next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| GitHub Issue Reader this skilljumppad-labs/jumppad | 263 | — | ~958 | Automated safety check: Pass | MPL-2.0 | |
| Ask NavigatorYeachan-Heo/oh-my-claudecode | 40k | — | ~4.1k | Automated safety check: Pass | MIT | |
| PRP Implementation PlannerWirasm/prp | 2.3k | — | ~4.1k | Automated safety check: Pass | MIT | |
| PRP PlanWirasm/prp | 2.3k | — | ~4k | Automated safety check: Pass | MIT | |
| Dev RequestFHIR/fhir-codegen | 154 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Feature Spec Generatorcashew-labs/libretto | 904 | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
PRP Implementation Planner
Wirasm/prp
Turns a PRD, issue or description into an implementation-ready plan grounded in codebase evidence, adding root-cause analysis for bugs and publishing issue plans back to the issue.
PRP Plan
Wirasm/prp
Writes an implementation-ready plan for a feature, bug fix, refactor or chore from a PRD, issue or description, grounded in codebase evidence, and can post it back to the source issue.
Dev Request
FHIR/fhir-codegen
Drafts and iterates on local-development feature requests in the role of a staff-level Product Manager.
Feature Spec Generator
cashew-labs/libretto
Researches the codebase and relevant docs, asks clarifying questions, then writes a spec sheet in specs/ for a significant feature or complex fix.
TiXL Ticket Processor
tixl3d/tixl
Works through the In progress column of the TiXL road-map board unattended, turning simple tickets into git stashes and writing plans for the rest under .agentic/Plans.
More from jumppad-labs/jumppad
All 8 skills in this repoGo Development Guidelines
jumppad-labs/jumppad
Sets idiomatic Go conventions with a test-first workflow, using testify/require for assertions and mockery for mocks, for new features, packages and refactors.
Spektacular Plan Implementation
jumppad-labs/jumppad
Executes an approved plan step by step through the spektacular CLI, which acts as the state machine, producing code, tests and a changelog.
Interactive Implementation Planner
jumppad-labs/jumppad
Builds detailed implementation plans through interactive questions, parallel research agents and template files for context, research, plan and tasks, from an issue or a plan name.
Spektacular Knowledge Base Playbook
jumppad-labs/jumppad
Routes natural-language requests to look up, add or update entries in a project's knowledge store by calling the spektacular knowledge CRUD commands directly, without a multi-step CLI flow.
Spek Manage Repos
jumppad-labs/jumppad
Add a repo to the current Spektacular project through a guided conversation, inspect the registry, and repair a repo's footprint.
Spek New
jumppad-labs/jumppad
Create a new Specification for a feature. An agent skill from jumppad-labs/jumppad.
Related
Works with
Categories
Questions about GitHub Issue Reader
What does GitHub Issue Reader do?
Pulls a GitHub issue's description, comments, labels, assignees, milestone and linked pull requests into one markdown report so the agent can plan a fix. py, that collects everything attached to a GitHub issue and prints it as formatted markdown. The report covers the title, URL, open or closed state, author, timestamps, labels, assignees, milestone, the full description and every comment with its author and time.
When should I use GitHub Issue Reader?
GitHub Issue Reader fits situations like: planning a fix for a specific GitHub issue; gathering requirements from an issue thread before coding starts; checking which pull requests are already linked to an issue; reviewing the history and discussion of a long-running issue.
How do I install GitHub Issue Reader in Claude Code?
Run `npx skills add jumppad-labs/jumppad --skill github-issue-reader -a claude-code`. Or copy the skill folder (.claude/skills/github-issue-reader in jumppad-labs/jumppad) into .claude/skills/github-issue-reader in your project. Claude Code loads it when a task matches its description.
How do I install GitHub Issue Reader in Codex?
Run `npx skills add jumppad-labs/jumppad --skill github-issue-reader -a codex`. Or copy the skill folder (.claude/skills/github-issue-reader in jumppad-labs/jumppad) into .agents/skills/github-issue-reader in your project. Codex loads it when a task matches its description.
Can I use GitHub Issue Reader in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jumppad-labs/jumppad --skill github-issue-reader -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-issue-reader, .gemini/skills/github-issue-reader, .github/skills/github-issue-reader and .opencode/skills/github-issue-reader in your project.
What does GitHub Issue Reader need to run?
Going by SKILL.md and its folder, GitHub Issue Reader needs Python for the scripts in its folder and the command-line tools its instructions call (gh). Our summary lists: GitHub CLI (gh), installed and authenticated; Python to run scripts/fetch_issue.py.
Does GitHub Issue Reader access the network?
SKILL.md names 2 domains. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. As links in the text: cli.github.com. This is read from the text; nothing was executed.
Is GitHub Issue Reader safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does GitHub Issue Reader use?
GitHub Issue Reader is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does GitHub Issue Reader use?
About 958 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to GitHub Issue Reader?
Skills that share tags, products or a category with GitHub Issue Reader: Ask Navigator (Yeachan-Heo/oh-my-claudecode, 40k stars), PRP Implementation Planner (Wirasm/prp, 2.3k stars), PRP Plan (Wirasm/prp, 2.3k stars) and Dev Request (FHIR/fhir-codegen, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GitHub Issue Reader?
jumppad-labs (a GitHub organization) maintains it in jumppad-labs/jumppad, which has 263 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 1, 2026.
Source: jumppad-labs/jumppad on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.