gh-issues

Automate GitHub issue discovery and fixes with parallel sub-agents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gh-issues orchestrates automated discovery, triage, and fixes for GitHub issues by spawning parallel sub-agents to implement code changes and open pull requests, reducing manual review time and human effort.

Core Features & Use Cases

  • Fetch and filter issues by owner/repo, labels, milestones, and assignees
  • Spawn multiple sub-agents in parallel to propose and open PRs
  • Monitor PR reviews and automatically address feedback
  • Support watch mode (continuous polling) and cron mode (scheduled runs)
  • Optional fork mode for pushing fixes to a fork before PRing to the source repo
  • Token-based authentication via GH_TOKEN and curl-based GitHub REST API

Quick Start

Run /gh-issues with your target repository and options to start processing issues automatically.

Frequently Asked Questions about gh-issues

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

FAQPage Schema
How do I automatically fix GitHub issues and open pull requests?

Automating GitHub issue fixes involves spawning parallel sub-agents to implement code changes and open pull requests. The process uses curl-based GitHub REST API calls to fetch, triage, and resolve issues with minimal manual effort.

Can I filter which GitHub issues are processed by labels and milestones?

Yes, you can filter GitHub issues by owner and repository, as well as by specific labels, milestones, and assignees. This ensures the parallel sub-agents only process relevant issues that meet your project criteria.

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

Yes, token-based authentication via GH_TOKEN is required. It authorizes the curl-based GitHub REST API calls needed to fetch issues, push fixes to repositories or forks, and open pull requests.

Does GitHub issue automation support continuous polling or scheduled cron modes?

Yes, the automation supports watch mode for continuous polling and cron mode for scheduled runs. These modes monitor pull request reviews and automatically address feedback over time.

What is fork mode for opening pull requests in GitHub issue automation?

Fork mode pushes automated code fixes to a forked repository before opening a pull request to the source repository. This allows sub-agents to propose changes without direct write access to the original project.

What are the limitations of using parallel sub-agents for GitHub issue resolution?

The automation relies on curl-based GitHub REST API calls and requires proper GH_TOKEN setup. While it orchestrates parallel sub-agents to fix issues, complex repository-specific logic may still require manual PR review and human oversight.