skills.rest
HomericIntelligence
HomericIntelligenceOFFICIAL
Explore all skills by this author →
GitHub

gh-read-issue-context

Retrieve GitHub issue body, comments, labels, assignees, and linked pull requests.

18|5|Updated Nov 3, 2025
Search Tags:#workflow#developer tools#context#github#cli#issue
One-click install
npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill gh-read-issue-context-homericintelligence
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-read-issue-context
Source: https://github.com/HomericIntelligence/ProjectOdyssey/tree/main/.claude/skills/gh-read-issue-context
Command: npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill gh-read-issue-context-homericintelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of gathering all relevant information from a GitHub issue, ensuring no critical context is missed before starting or resuming work.

Core Features & Use Cases

  • Comprehensive Context Retrieval: Fetches issue body, comments, labels, assignees, and linked pull requests.
  • Status and History Tracking: Checks issue state, closure reasons, and implementation history.
  • Use Case: Before starting a new feature implementation, use this Skill to review the issue's description, all discussion in comments, and any existing pull requests to understand the requirements and prior work.

Quick Start

Use the gh-read-issue-context skill to retrieve all information for GitHub issue number 123.

Frequently Asked Questions about gh-read-issue-context

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

FAQPage Schema
How do I gather full context from a GitHub issue before starting development?▼

GitHub issue context involves fetching the issue body, comments, labels, assignees, and linked pull requests. This comprehensive retrieval ensures no critical context is missed before starting or resuming software development work.

What GitHub issue details do I need for efficient issue triage?▼

Efficient issue triage requires reviewing the issue body, all discussion in comments, current state, closure reasons, assignees, and linked pull requests. Checking implementation history helps understand requirements and prior work.

Do I need the GitHub CLI to retrieve issue context and linked pull requests?▼

Yes, retrieving GitHub issue context requires the GitHub CLI (gh) for authenticated access and data retrieval operations. It facilitates fetching comprehensive issue details including linked pull requests and implementation history.

Can I track issue status and implementation history using GitHub CLI?▼

Yes, you can track issue status and implementation history using GitHub CLI. It retrieves the issue state, closure reasons, and linked pull requests to facilitate progress tracking in software development workflows.

What's the best way to review GitHub issue discussions and prior work before implementation?▼

The best way to review GitHub issue discussions is to retrieve all context including the issue description, comments, and existing pull requests. This allows you to fully understand requirements and prior work before implementation.

Related Skills

Explore More Software Engineering Skills→
vaclavbenesvaclavbenes

github

Automate GitHub repository, code, pull request, and issue operations via gh CLI.

Community
Intermediate
BrennonTWilliamsBrennonTWilliams
7

ll-scan-codebase

Scan project directories to identify bugs and generate structured issue files.

Community
Intermediate
NagyViktNagyVikt
2

yeet

Automate GitHub publishing from branch creation to draft pull request.

Community
Advanced
ma08ma08
28

gh-address-comments

Fetches and triages GitHub PR comments via CLI.

Community
Intermediate