gh-issues

Automate GitHub issue triage, fixes, and PR creation via the REST API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing GitHub issues, fixes, and PRs across multiple repos and forks is tedious and slow. This Skill automates triage, task delegation, and PR creation by orchestrating parallel sub-agents that implement changes and monitor review cycles.

Core Features & Use Cases

  • Fetch and filter issues from a repository (by label, milestone, assignee) and optionally watch for new items.
  • Spawn parallel sub-agents to implement fixes, push branches (to source or fork), and open PRs.
  • Monitor PR reviews and spawn follow-up agents to address comments, enabling end-to-end automation of issue resolution.

Quick Start

Invoke the /gh-issues command for a repository to automatically fetch issues, spawn fix agents, 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?

You can automate fixing GitHub issues by orchestrating parallel sub-agents that implement changes, push branches, and open PRs automatically. This workflow fetches issues, delegates fixes to agents, and monitors PR reviews to address comments end-to-end.

Can I filter GitHub issues by label or milestone before automating fixes?

Yes, you can filter GitHub issues by label, milestone, or assignee before spawning fix agents. This ensures the parallel sub-agents only process specific subsets of issues that match your triage criteria across source repositories and forks.

How does parallel sub-agent orchestration work for GitHub issue resolution?

Parallel sub-agent orchestration for GitHub issue resolution works by spawning multiple agents simultaneously to implement fixes, push branches, and open PRs. It then monitors PR reviews and spawns follow-up agents to address comments continuously.

Do I need the GitHub CLI installed to automate issue triage and PR creation?

No, you do not need the GitHub CLI installed to automate issue triage and PR creation. The workflow uses the GitHub REST API via curl for all remote verification, token handling, and pull request operations without relying on the gh CLI.

Can I continuously watch for new GitHub issues and process them automatically?

Yes, you can continuously watch for new GitHub issues and process them automatically using optional cron or watch modes. These modes continuously fetch new items, spawn parallel fix agents, and monitor PR reviews for follow-up actions.

What is the best way to manage GitHub PR review comments with automated agents?

The best way to manage GitHub PR review comments with automated agents is by monitoring review cycles and spawning follow-up sub-agents. These agents automatically address comments, enabling end-to-end automation of issue resolution and PR updates.