gh-issues

Fetch GitHub issues via REST API and spawn parallel sub-agents to implement fixes and open PRs.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/abhiunix/community-registry --skill gh-issues-abhiunix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issues
Source: https://github.com/abhiunix/community-registry/tree/main/skills/development/gh-issues
Command: npx skills add https://github.com/abhiunix/community-registry --skill gh-issues-abhiunix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines triaging GitHub issues by fetching issues, spawning specialized sub-agents to implement fixes, opening PRs, and monitoring review feedback.

Core Features & Use Cases

  • Fetch issues from a repository with filters for labels, milestones, assignees, and state.
  • Spawn parallel sub-agents to create fixes and PRs, and monitor review comments.
  • Support fork mode, watch/cron modes, and model selection for agents.

Quick Start

Invoke /gh-issues with a repository in the form owner/repo and optional flags to begin automatic issue processing.

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 automatically open PRs?

To automate GitHub issue fixes, this Skill fetches issues via REST API and spawns parallel sub-agents to implement fixes and open PRs. It orchestrates the entire workflow from triaging to pull request creation automatically.

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

Yes, you need a GH_TOKEN for authentication to fetch and orchestrate GitHub issues. The workflow relies on this token to execute REST API calls via curl for pre-flight checks and claim-based task tracking.

Can I use fork mode when spawning parallel agents to fix GitHub issues?

Yes, the workflow supports fork mode when spawning parallel sub-agents to implement fixes. It also includes optional watch scheduling, cron modes, and model selection for the sub-agents.

How does claim-based task tracking work for automated GitHub issue processing?

Claim-based task tracking prevents overlapping work by checking pre-flight conditions and existing PRs before assigning issues. The workflow ensures sub-agents only process unclaimed GitHub issues to avoid duplicate PRs.

What is the best way to monitor review feedback on PRs opened by automated sub-agents?

The best way to monitor review feedback is through the Skill's built-in watch mode, which continuously monitors review comments on opened PRs. This allows the parallel fix agents to track and respond to automated issue resolutions.