gh:issue-read

Fetch a GitHub issue by number and print a structured verbatim summary.

Updated May 31, 2025

Search Tags:#automation #github #cli #issue #summary #read-only

Ready to run

npx skills add https://github.com/dEitY719/dotfiles --skill gh-issue-read

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gh:issue-read
Source: https://github.com/dEitY719/dotfiles/tree/main/claude/skills/gh-issue-read
Command: npx skills add https://github.com/dEitY719/dotfiles --skill gh-issue-read

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enables read-only retrieval of a GitHub issue by number and outputs a structured, verbatim summary suitable for downstream tasks, preserving body and comments for perfect context.

Core Features & Use Cases

Read-only issue retrieval: Fetch the issue data without mutating it.
Structured output: Produce a multi-section summary (Header, Summary, Body, Discussion, Meta, Checklist) for clear understanding.
Language-agnostic: Preserves content language, adapting section headers to match user language when needed.
Use Case: A developer or product manager wants a precise, artifact-like summary of an issue to brief a teammate or plan work without parsing raw GitHub UI.

Quick Start

Run the skill to fetch a specific issue by number and print a structured, verbatim summary.

Frequently Asked Questions about gh:issue-read

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

FAQPage Schema

How do I get a structured GitHub issue summary for quick context?▼

Retrieve a structured GitHub issue summary by fetching the issue by number to produce a multi-section, verbatim output including Header, Summary, Body, Discussion, Meta, and Checklist for clear context.

Can I read GitHub issue content and comments without modifying the repository?▼

Yes, you can read GitHub issue content without modifying the repository through a read-only retrieval process that fetches issue data via gh issue view and preserves the body and comments verbatim.

What is the best way to extract GitHub issue context for downstream planning tasks?▼

The best way to extract GitHub issue context for downstream planning is to generate a structured summary that preserves body and comments perfectly, providing an artifact-like briefing for implementation across repositories.

Does the GitHub issue summary preserve the original language of the issue body?▼

Yes, the GitHub issue summary preserves the original language of the issue body and comments, functioning as a language-agnostic retrieval that adapts section headers to match the user's language when needed.

How do I fetch a specific GitHub issue by number using the command line?▼

You fetch a specific GitHub issue by number using the command line by executing gh issue view with specific fields to resolve the target repo from a given remote and print a structured summary.