github-issue-context

Retrieve GitHub issue body, labels, assignees, and comments as JSON.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/soygabimoreno/Los-ANDROIDES --skill github-issue-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-context
Source: https://github.com/soygabimoreno/Los-ANDROIDES/tree/main/.agents/skills/github-issue-context
Command: npx skills add https://github.com/soygabimoreno/Los-ANDROIDES --skill github-issue-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents guessing by giving you the complete, up-to-date information from a GitHub issue (including body, comments, labels, assignees, and any linked PRs) before you propose changes.

Core Features & Use Cases

  • Issue body + comment digestion: Captures the original ask and the latest discussion so you understand the real constraints and direction.
  • Thread-aware decision extraction: Highlights pivots and outcomes discussed across the conversation.
  • Linked PR discovery: Surfaces related PRs that mention or are associated with the issue number, helping you avoid duplicating work.

Quick Start

Use this skill when you see an issue URL like github.com/soygabimoreno/Los-ANDROIDES/issues/123 or a reference like #123, and ask what to do next based on the resulting context block.

Frequently Asked Questions about github-issue-context

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

FAQPage Schema
How do I load complete GitHub issue context before proposing a fix?

Loading complete GitHub issue context retrieves the body, labels, assignees, and all comments to prevent guessing before proposing changes. It uses gh issue view for structured JSON to capture the original ask and the latest discussion so you understand the real constraints and direction.

Can I find linked pull requests for a GitHub issue automatically?

Finding linked pull requests for a GitHub issue is possible by optionally fetching related PRs via the gh pr list command. This surfaces related PRs that mention or are associated with the issue number, helping you avoid duplicating work during implementation planning.

What is the best way to extract actionable decisions from long GitHub issue threads?

Extracting actionable decisions from GitHub issue threads involves thread-aware decision extraction that highlights pivots and outcomes discussed across the conversation. This process captures the original ask and the latest discussion to produce a compact context block determining the correct solution direction.

Does resolving GitHub issue context require write actions or permissions?

Resolving GitHub issue context does not require write actions. The process strictly retrieves the issue body, comments, and linked PRs to produce a compact context block without performing any write actions, ensuring a read-only review of the correct intent and recent discussion.

How do I triage a GitHub issue reference like #123 for implementation planning?

To triage a GitHub issue reference like #123 for implementation planning, resolve the issue number and use gh issue view to retrieve structured JSON. This captures the full issue context, including recent discussion and assignees, to determine the correct solution direction without guessing.