gh-issues

Orchestrate parallel sub-agents to fix GitHub issues and open PRs via REST API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gh-issues orchestrates automated fixing by creating and coordinating parallel sub-agents to process GitHub issues and open PRs using REST API calls exclusively.

Core Features & Use Cases

It supports source and fork workflows, filters issues by label, milestone, assignee, and state, and can run in watch or cron modes with token resolution and pre-flight checks. The orchestrator also tracks progress across multiple issues, spawns dedicated agents to implement fixes, and automatically opens PRs when ready.

Quick Start

Invoke gh-issues with a repository to begin fetching issues, spawning sub-agents to fix them, and monitor PR reviews.

Frequently Asked Questions about gh-issues

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

FAQPage Schema
How do I automate fixing GitHub issues and opening pull requests in parallel?

An orchestrator automates fixing GitHub issues by spawning parallel sub-agents to implement fixes, track progress, and open pull requests automatically via GitHub REST API calls.

How do I filter GitHub issues by label, milestone, or assignee for automated processing?

You can filter GitHub issues by label, milestone, assignee, and state parameters, allowing the orchestrator to fetch and process only matching issues via GitHub REST API calls.

Do I need a GitHub token to run automated issue fixing workflows?

Yes, a GH_TOKEN is required to authenticate GitHub REST API calls for fetching issues, spawning sub-agents, and managing pull requests, sourced from OpenClaw config if not provided.

Can I run automated GitHub issue processing in watch or cron modes?

Yes, automated GitHub issue processing supports watch and cron modes, enabling continuous monitoring or scheduled execution of issue fetching, sub-agent coordination, and PR management.

Does automated GitHub issue fixing support both source repo and fork workflows?

Yes, automated GitHub issue fixing supports both source repository and fork workflows, allowing sub-agents to process issues and open pull requests from either workflow via GitHub REST API.

What are the limitations of using REST API calls for GitHub issue automation?

REST API-based GitHub issue automation relies on curl for all operations, requiring valid GH_TOKEN authentication and pre-flight checks to manage rate limits and ensure successful PR creation.