gh-issues

Automate GitHub issue triage, fix execution, and PR review monitoring.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Arry8/openclaw-edge --skill gh-issues-arry8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-issues
Source: https://github.com/Arry8/openclaw-edge/tree/main/skills/gh-issues
Command: npx skills add https://github.com/Arry8/openclaw-edge --skill gh-issues-arry8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates GitHub issue triage and PR fix workflows by coordinating multiple sub-agents to fetch issues, implement fixes, and open pull requests, while monitoring review comments.

Core Features & Use Cases

  • Fetch issues from a repository with filters (labels, milestones, assignees) and spawn sub-agents to handle fixes.
  • Open PRs on the source or a fork, monitor PR reviews, and spawn follow-up agents as needed.
  • Supports cron and watch modes, fork mode, and model customization for sub-agents.

Quick Start

Call /gh-issues with the target owner/repo and optional flags to automatically 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 automate GitHub issue triage and PR fixes across multiple repositories?▼

Automating GitHub issue triage involves fetching issues with filters and spawning dedicated sub-agents to implement fixes. This orchestrator coordinates opening pull requests and monitors PR review comments across multiple repositories.

Can I use cron and watch modes for automated GitHub pull request monitoring?▼

Yes, cron and watch modes are supported for automated GitHub pull request monitoring. These modes enable continuous scheduling and real-time tracking of issue triage, sub-agent spawning, and PR review handling.

Does GitHub issue automation support fork mode and token-based API access?▼

GitHub issue automation supports fork mode for opening pull requests and satisfies token-based API access. It allows configurable sub-agent spawning and model customization for executing repository fixes.

What is the best way to orchestrate sub-agents for GitHub issue resolution?▼

Orchestrating sub-agents for GitHub issue resolution requires a scalable coordinator that fetches issues, spawns dedicated agents to implement fixes, and opens PRs. This approach handles follow-up agents based on PR review comments.

How do I filter GitHub issues by labels, milestones, or assignees before spawning fix agents?▼

Filtering GitHub issues by labels, milestones, and assignees happens before spawning sub-agents to handle fixes. The orchestrator fetches issues matching these criteria and applies configurable sub-agent spawning for targeted resolution.