gh-issues

Fetch GitHub issues, spawn parallel fix agents, and open pull requests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates the discovery and automated handling of GitHub issues by spawning parallel sub-agents to implement fixes and open PRs, then monitoring PR reviews.

Core Features & Use Cases

  • Spawn parallel sub-agents to implement fixes and open PRs
  • Monitor PR reviews and address feedback
  • Supports fork mode for pushing branches and PRs from a fork
  • Cron and watch modes to automatically poll for new issues and scale processing
  • End-to-end authentication, issue listing, PR creation, and result tracking via curl + GitHub REST API

Quick Start

Fetch open issues from a repository and automatically spawn parallel fix agents to propose changes and open PRs.

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?

You can automate GitHub issue fixes by spawning parallel sub-agents to implement patches and open pull requests. The process uses curl-based GitHub REST API calls to fetch issues, coordinate agent fixes, and track PR results automatically.

Can I automatically monitor GitHub pull request reviews and address feedback?

Yes, you can monitor pull request reviews and address feedback automatically. After spawning sub-agents to open initial PRs, the orchestration continues tracking review status via the GitHub REST API to resolve requested changes.

Does this automated GitHub issue handling support fork mode for pushing branches?

Automated GitHub issue handling supports fork mode for pushing branches and opening pull requests from a fork. This isolates automated sub-agent patching changes away from the main repository before review.

How do I continuously poll for new GitHub issues to scale automated processing?

You continuously poll for new GitHub issues using built-in cron and watch modes. These modes automatically trigger the issue fetching and parallel sub-agent spawning processes to scale ongoing repository maintenance tasks.

Do I need a GitHub token to authenticate automated issue triage and patching?

Yes, you need a GitHub token to authenticate automated issue triage and patching. The orchestration performs token validation via curl-based GitHub REST API calls before listing issues, spawning agents, and creating pull requests.