gh-issues

Fetch and manage GitHub issues by spawning sub-agents to implement fixes and open PRs.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/zyj18860969891-byte/openclaw-railway --skill gh-issues-zyj18860969891-byte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issues
Source: https://github.com/zyj18860969891-byte/openclaw-railway/tree/main/skills/gh-issues
Command: npx skills add https://github.com/zyj18860969891-byte/openclaw-railway --skill gh-issues-zyj18860969891-byte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gh-issues orchestrates the end-to-end handling of GitHub issues by spawning sub-agents that implement fixes, open PRs, and monitor PR reviews.

Core Features & Use Cases

  • Automates the lifecycle of issues: fetches, analyzes, and schedules fixes via parallel sub-agents
  • Fork-mode support: pushes branches to a fork and opens PRs from fork to source repo
  • Watches for new issues and PR review comments, then reacts automatically or on demand
  • Flexible filtering: labels, milestones, assignees, and PR state with cron and watch modes

Quick Start

Run /gh-issues on a repository to auto-fetch issues, spawn fix agents, and create PRs.

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 fixes and pull request creation?

To automate GitHub issue fixes, you can use a skill that fetches issues via the GitHub REST API and spawns sub-agents to implement code fixes and open pull requests automatically. This orchestration handles the end-to-end lifecycle from issue tracking to PR submission.

Can I automatically create pull requests from a fork to the source repository?

Yes, you can create pull requests from a fork to the source repository using fork-mode support. The automation pushes branches to your fork and opens PRs directly against the original source repository, streamlining the contribution workflow.

Do I need a GitHub token to automate issue management and PR monitoring?

Yes, you need a valid GH_TOKEN to automate issue management and PR monitoring. All GitHub operations use curl with the GitHub REST API, and the system includes built-in token resolution and safety checks to ensure secure access.

How can I filter GitHub issues for automated processing using labels and milestones?

You can filter GitHub issues for automated processing by specifying labels, milestones, and assignees. This allows the sub-agents to target specific subsets of issues, ensuring that only relevant tasks are fetched and scheduled for fixes.

What is the best way to monitor new GitHub issues and PR review comments automatically?

The best way to monitor new GitHub issues and PR review comments automatically is by using watch and cron polling modes. These modes continuously check for new issues and review comments, then trigger sub-agents to react automatically or on demand.

How does spawning sub-agents help with GitHub issue orchestration?

Spawning sub-agents helps with GitHub issue orchestration by enabling parallel processing of fixes. Each sub-agent independently analyzes an issue, implements the necessary code changes, and opens a PR, allowing multiple issues to be resolved simultaneously.