gh-issues

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

202|36|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/adoresever/AGI_Ananas --skill gh-issues-adoresever
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issues
Source: https://github.com/adoresever/AGI_Ananas/tree/main/26.2.21openclaw-viking/skills/gh-issues
Command: npx skills add https://github.com/adoresever/AGI_Ananas --skill gh-issues-adoresever

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill coordinates the end-to-end workflow of triaging GitHub issues across repositories by spawning parallel sub-agents to implement fixes, open PRs, and monitor review comments.

Core Features & Use Cases

  • Orchestrates issue triage across multiple repositories
  • Spawns sub-agents to implement fixes and create PRs
  • Monitors PR reviews and addresses comments automatically

Quick Start

Run the /gh-issues command with a target owner/repo to begin fetching issues and spawning sub-agents.

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 across multiple repositories?

You can automate GitHub issue fixes by running the command with a target owner/repo to fetch issues and spawn sub-agents that implement the fixes and open pull requests automatically.

Can I monitor and address GitHub PR review comments automatically?

Yes, you can monitor and address PR review comments automatically. After sub-agents open pull requests, the skill continuously monitors reviews and addresses comments to resolve feedback without manual oversight.

Does this GitHub issue automation support fork mode, cron, and watch polling?

Yes, the GitHub issue automation supports multi-repo workflows including fork mode, cron scheduling, and watch polling, enabling continuous triage and automated fixes across repositories.

How do sub-agents orchestrate issue triage using the GitHub REST API?

Sub-agents orchestrate issue triage by using curl and the GitHub REST API for all operations. They fetch target issues, implement the necessary code fixes in parallel, and submit pull requests directly to the repository.

Do I need to install extra dependencies to automate GitHub issues with sub-agents?

No extra dependencies are required to automate GitHub issues. The skill uses standard curl and the GitHub REST API for all operations, requiring no additional component installations.

What is the best way to coordinate end-to-end GitHub issue triage and PR monitoring?

The best way to coordinate end-to-end GitHub issue triage is using an orchestration skill that fetches issues, spawns sub-agents for fixes, and monitors PR reviews. This approach handles the full lifecycle from issue creation to review resolution.