gh-issues

Fetch GitHub issues and orchestrate sub-agents to open PRs and track reviews.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/Solitude01/proiect-new --skill gh-issues-solitude01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issues
Source: https://github.com/Solitude01/proiect-new/tree/main/%E5%88%9B%E6%84%8F/%E9%A3%9E%E7%89%9B/OPENCLAW/openclaw/openclaw/skills/gh-issues
Command: npx skills add https://github.com/Solitude01/proiect-new --skill gh-issues-solitude01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issue management is labor-intensive, requiring monitoring, filtering, and follow-ups across issues, PRs, and reviews. This skill automates discovery, agent orchestration, and PR creation to accelerate fixes.

Core Features & Use Cases

  • Auto-fetch issues from a repository with filters (labels, state, milestone, assignees).
  • Spawn sub-agents to implement fixes and open PRs, and monitor PR reviews.
  • Support fork workflows, cron and watch polling, and optional notifications.

Quick Start

Run /gh-issues to fetch issues for a repository and automatically 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 GitHub issue fixes and pull request creation?

Automating GitHub issue fixes uses sub-agents to fetch repository issues, generate code fixes, and open pull requests automatically. It orchestrates these tasks in parallel while tracking ongoing PR reviews.

Can I filter GitHub issues by labels or assignees before spawning automated agents?

Filtering GitHub issues by labels, state, milestone, or assignees is supported before automated agents process them. This ensures sub-agents only fetch and act on the specific repository issues matching your criteria.

Does this automated issue orchestration work with forked repositories and cron polling?

Forked repository workflows and cron or watch polling are supported for automated issue orchestration. This allows continuous monitoring of issues and PR reviews across both standard and forked GitHub repository configurations.

How do sub-agents monitor GitHub PR reviews after opening a pull request?

Sub-agents monitor GitHub PR reviews by fetching review states via REST API calls after opening a pull request. They track the review status to ensure automated fixes progress correctly through the repository's review workflow.

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

A GitHub token is required for REST API authentication to fetch issues, open PRs, and monitor reviews. The skill resolves tokens through argument parsing to execute parallel sub-agent task spawning securely.

What is the best way to handle multiple GitHub issues in parallel?

Handling multiple GitHub issues in parallel is done by spawning sub-agents for each filtered issue, utilizing REST API calls via curl. Optional model configurations and notification channels can be applied to manage the parallel orchestration.