gh-issues

Fetch GitHub issues, spawn sub-agents to implement fixes, and open PRs.

330|61|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/eggent-ai/eggent --skill gh-issues-eggent-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issues
Source: https://github.com/eggent-ai/eggent/tree/main/bundled-skills/gh-issues
Command: npx skills add https://github.com/eggent-ai/eggent --skill gh-issues-eggent-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gh-issues automates the process of fetching GitHub issues, spawning sub-agents to implement fixes and open PRs, and monitoring PR review comments to ensure closure.

Core Features & Use Cases

  • Orchestrates issue retrieval with filters (labels, milestones, assignees) and supports fork workflows.
  • Spawns parallel sub-agents to generate code changes, create branches, and open PRs while tracking progress.
  • Monitors PR reviews and triggers follow-up actions or additional fixes as needed.

Quick Start

Invoke the gh-issues command with /gh-issues owner/repo and optional flags to start fetching issues and spawning fix agents.

Frequently Asked Questions about gh-issues

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

FAQPage Schema
How do I automate GitHub issue triage and PR fixes?

You can automate GitHub issue triage by using a command to fetch filtered issues and spawn parallel sub-agents that implement fixes and open PRs. Invoke it with owner/repo and optional flags for labels or milestones.

How does sub-agent orchestration work for GitHub issues?

Sub-agent orchestration works by spawning parallel agents to generate code changes, create branches, and open PRs for fetched GitHub issues. It tracks progress and monitors PR review comments to trigger follow-up actions or additional fixes as needed.

Do I need a GitHub token to automate issue fixes and open PRs?

Yes, you need a required GH_TOKEN to automate opening PRs from GitHub issues. The automation uses the GitHub REST API via curl, performing pre-flight checks with this token to authenticate and manage repository workflows.

Can I filter GitHub issues by labels, milestones, and assignees during triage?

Yes, you can filter GitHub issues by labels, milestones, and assignees during triage. The orchestration retrieves issues based on these filters and supports fork workflows to generate code changes and open PRs in parallel.

Does GitHub issue automation support fork workflows and cron polling?

Yes, GitHub issue automation supports fork workflows and cron-based polling. The cron polling is used to monitor PR reviews, ensuring that follow-up actions or additional fixes are triggered when review comments are detected.

What are the limitations of automating PR fixes with sub-agents?

Automating PR fixes with sub-agents requires a GH_TOKEN and uses curl for GitHub REST API calls, meaning it is limited by API rate limits and token permissions. It relies on pre-flight checks and optional model or notify-channel parameters for execution.