gh-read-issue-context

Retrieving GitHub issue context compiles issue details, comments, labels, assignees, linked PRs, and timeline into structured JSON output. Use gh-read-issue-context to extract this data via the gh CLI, exposing fields needed for downstream parsing and implementation decisions without manually gathering scattered information.

Yes. The Skill parses issue body, comments, and metadata to surface critical information like design decisions and blockers. Combined with keyword parsing, you can quickly identify key constraints and prior discussions from all comments and linked context.

The gh CLI exposes issue metadata including title, body, comments, labels, assignees, milestone, state, and linked pull requests. This structured JSON output feeds directly into documentation, analysis, or downstream automation tools that require comprehensive issue context.

GitHub issue context retrieval includes related data like linked PRs and timeline events alongside the core issue metadata. The Skill compiles these via gh issue view, providing full relational context for understanding prior work and design rationale.

Yes. The Skill requires only gh and jq, both standard in GitHub Actions and command-line environments. JSON output integrates cleanly into scripts, automation workflows, and documentation pipelines that need structured issue data.

Retrieving full issue context systematically captures all prior discussions, decisions, and linked work in one operation. This prevents gaps when returning to a task after a break and ensures implementation decisions align with documented requirements and constraints.