gh-issues

Fetch GitHub issues and spawn parallel sub-agents to open PRs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments.

Core Features & Use Cases

  • Fetch issues from a repository and filter by labels, milestones, and assignees.
  • Spawn parallel sub-agents to generate fixes and open PRs, then monitor review comments and update PRs.
  • Support fork workflows, cron mode, and watch mode for continuous automation.

Quick Start

Run /gh-issues with a target owner/repo and optional filters to fetch issues and auto-spawn 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 issues by spawning agents to open pull requests?

To automate GitHub issues, this Skill enumerates open issues from a target repository and spawns parallel sub-agents to propose fixes and open pull requests. It handles the entire triage lifecycle from fetching to PR review handling.

What is the best way to automatically triage GitHub issues and generate fixes?

The best way to triage GitHub issues automatically is using an orchestration Skill that fetches issues via the GitHub REST API and spawns parallel sub-agents to generate fixes. This approach supports filters like labels, milestones, and assignees.

Do I need a GH_TOKEN to automate pull request creation from GitHub issues?

Yes, you need a GH_TOKEN to automate pull request creation from GitHub issues. The Skill uses curl with the GitHub REST API and respects the GH_TOKEN environment variable for authenticating all issue fetching and PR opening operations.

Can I filter GitHub issues by labels, milestones, or assignees before spawning fix agents?

You can filter GitHub issues by labels, milestones, and assignees before spawning fix agents. The Skill supports these filters during the argument parsing and issue fetching phases to ensure only relevant issues are processed.

Does GitHub issue orchestration work with fork workflows and continuous cron mode?

GitHub issue orchestration works with fork workflows, cron mode, and watch mode for continuous automation. These optional modes allow the Skill to operate persistently, monitoring issues and addressing PR review comments over time.

Why does my automated GitHub issue agent fail during pre-flight checks or PR review handling?

Automated GitHub issue agents may fail during pre-flight checks if the GH_TOKEN lacks repository permissions or the target owner/repo is invalid. The Skill operates across multiple phases including pre-flight checks and PR review handling to validate the environment.