github-issue

agentuity's avatarfrom agentuity

Fetch a GitHub issue and generate a plan to resolve it

⭐12stars🔀1forks📁View on GitHub🕐Updated Jan 4, 2026

When & Why to Use This Skill

This Claude skill streamlines the software development lifecycle by fetching GitHub issues and generating structured, actionable resolution plans. It bridges the gap between issue tracking and implementation by providing developers with clear, step-by-step guidance for codebase analysis, implementation, and testing, significantly reducing the time spent on manual triage and planning.

Use Cases

  • Automated Issue Triage: Quickly fetch and analyze GitHub bug reports to generate an immediate technical plan for resolution without leaving the chat interface.
  • Feature Implementation Roadmaps: Convert high-level feature requests into detailed implementation checklists, including specific steps for coding and testing.
  • Developer Context Gathering: Automatically pull issue descriptions, labels, and comments to provide the AI with full context for complex debugging tasks.
  • Workflow Efficiency: Use the GitHub CLI integration to reduce context switching between the browser, terminal, and IDE during the initial phases of a task.
namegithub-issue
descriptionFetch a GitHub issue and generate a plan to resolve it

GitHub Issue Skill

This skill helps you work on GitHub issues by fetching the issue details and generating a structured plan for resolution.

Usage

When the user wants to work on a GitHub issue, use the fetch-issue tool to get the issue details:

fetch-issue 123
fetch-issue https://github.com/agentuity/sdk/issues/123

Workflow

  1. Fetch the Issue: Use the fetch-issue tool with the issue number or URL
  2. Analyze the Output: The tool returns the issue details including title, description, labels, comments, and resolution instructions
  3. Follow the Plan: The output includes step-by-step instructions for:
    • Understanding the issue
    • Analyzing the codebase
    • Creating an implementation plan
    • Implementing the solution
    • Testing the changes
    • Summarizing the work

Requirements

  • GitHub CLI (gh) must be installed and authenticated
  • Run gh auth login if not already authenticated