gh-issues

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

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/seasonmac/Full-Scene-Agents --skill gh-issues-seasonmac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issues
Source: https://github.com/seasonmac/Full-Scene-Agents/tree/main/openclaw/skills/gh-issues
Command: npx skills add https://github.com/seasonmac/Full-Scene-Agents --skill gh-issues-seasonmac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetch and manage GitHub issues by spawning parallel sub-agents to implement fixes and coordinate PRs, then monitor review comments to drive closure.

Core Features & Use Cases

  • Automatic issue triage: fetches issues with filters (labels, milestone, assignee) and ignores PRs.
  • Parallel sub-agent orchestration: creates multiple fixers concurrently or in cron mode, with claim-based tracking and watch support.
  • PR lifecycle automation: opens PRs from forks or the source repo, and handles PR review automation.

Quick Start

Run /gh-issues owner/repo [flags] to fetch issues, spawn fix sub-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 automatically fix GitHub issues and open pull requests?

To automatically fix GitHub issues, this Skill fetches issues from a target repository and spawns parallel sub-agents to implement fixes and open PRs. It operates against the source repository or an optional fork to push changes.

Can I filter which GitHub issues are processed by labels or assignees?

Yes, you can filter GitHub issues processed by labels, milestones, assignees, and states. The Skill fetches issues matching these specific filters while ignoring pull requests during the triage process.

How do I orchestrate parallel agents to resolve GitHub issues on a schedule?

You can orchestrate parallel agents to resolve GitHub issues on a schedule using cron mode. This creates multiple fixers concurrently with claim-based tracking, and watch mode supports continuous monitoring of PR reviews to drive closure.

Does the GitHub issue automation perform pre-flight checks before spawning sub-agents?

Yes, the GitHub issue automation enforces token resolution and performs pre-flight checks before spawning sub-agents. It verifies PR existence and branch status to ensure valid orchestration before initiating parallel fixes.

What is the best way to monitor GitHub PR review comments for automated issue closure?

The best way to monitor GitHub PR review comments for automated issue closure is using watch mode. It tracks PR review comments and coordinates with sub-agents to drive issue resolution and PR lifecycle automation to completion.