github-read

Name: github-read
Availability: InStock
Author: ebijun1007

Fetch GitHub issues and PRs with minimal gh CLI API calls.

Updated Aug 23, 2026

Search Tags:#github #issues #sub-issues #pull-requests #gh-cli #api-efficiency

Ready to run

npx skills add https://github.com/ebijun1007/vibe-coding --skill github-read

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-read
Source: https://github.com/ebijun1007/vibe-coding/tree/main/.codex/skills/github-read
Command: npx skills add https://github.com/ebijun1007/vibe-coding --skill github-read

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads GitHub issues and PRs efficiently by minimizing API calls, while ensuring related sub-issues and dependencies are tracked as needed.

Core Features & Use Cases

Minimal API usage: Retrieve essential fields using gh --json to reduce network traffic.
Hierarchical tracing: Navigate from parent issues to sub-issues and related items when relevant.
Use Case: When investigating a bug, start from the main issue and automatically surface linked tasks and related PRs to understand scope quickly.

Quick Start

Ask the AI to fetch the target issue or PR with minimal JSON data using gh --json.

Frequently Asked Questions about github-read

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fetch GitHub issues and PRs with minimal API calls?▼

To fetch GitHub issues and PRs with minimal API calls, use the gh CLI with the --json flag to retrieve only necessary fields, reducing network traffic while automatically surfacing linked sub-issues and related items for hierarchical tracing.

What's the best way to trace sub-issues and related PRs during bug triage?▼

Tracing sub-issues and related PRs during bug triage is handled by starting from a main issue and automatically navigating to linked tasks and dependencies, allowing you to understand the scope quickly without making excessive API calls.

Do I need the gh CLI installed to read GitHub issues efficiently?▼

Yes, you need the gh CLI installed to read GitHub issues efficiently, as this approach relies on its --json flag to minimize network traffic, though graceful fallbacks are included if gh is unavailable or results are too many.

How does --json reduce network traffic when pulling GitHub data?▼

The --json option reduces network traffic by querying and returning only the essential fields you specify from GitHub issues and PRs, rather than fetching full payloads, which optimizes API efficiency during debugging and review workflows.

What happens if gh is unavailable or returns too many GitHub issues?▼

If gh is unavailable or returns too many GitHub issues, the process includes graceful fallbacks to prevent failures, ensuring the workflow degrades safely without crashing when API limits are hit or the CLI is missing.

Can I use this approach to review pull requests across parent issues?▼

Yes, you can use this approach to review pull requests across parent issues, as it covers hierarchical tracing from parent issues to sub-issues and related PRs, efficiently surfacing linked items for debugging, triage, and review workflows.