gh-issues

Automate GitHub issue triage and PR creation via sub-agents.

1.3k|186|Updated Aug 14, 2025
One-click install
npx skills add https://github.com/google/adk-js --skill gh-issues-google
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issues
Source: https://github.com/google/adk-js/tree/main/tests/integration/skills/skills/gh-issues
Command: npx skills add https://github.com/google/adk-js --skill gh-issues-google

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gh-issues automates triage and automated fixes for GitHub issues by spawning parallel sub-agents to implement changes and open PRs, reducing manual toil.

Core Features & Use Cases

  • Orchestrates multi-phase workflows to fetch issues, spawn fix agents, and manage PRs
  • Supports token resolution, fork mode, cron-safe operation, pre-flight checks, and review handling
  • Useful for large repositories to automatically address bugs and improvements via PRs

Quick Start

Run /gh-issues with an owner/repo and optional flags to fetch issues, spawn sub-agents, and create 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 triage and fix multiple bugs in parallel?

Automate GitHub issue triage by spawning parallel sub-agents that implement fixes and open PRs. This workflow fetches issues based on filters, orchestrates fix agents across repositories, and manages pull requests to reduce manual toil for large projects.

How does automated sub-agent orchestration work for opening GitHub pull requests?

Sub-agent orchestration works through multi-phase workflows that fetch issues, spawn fix agents, and manage resulting PRs. It uses curl-based GitHub REST API calls, token resolution, and safety checks to coordinate parallel agents and handle reviews automatically.

Can I use cron jobs to automatically fix GitHub issues on a schedule?

Yes, you can use cron jobs to schedule automated GitHub issue fixes. The workflow supports cron-safe operation, allowing you to run triage, spawn sub-agents, and generate pull requests periodically without manual intervention.

Does automated GitHub issue fixing work with fork mode and repository filters?

Automated GitHub issue fixing supports both fork mode and repository filters. These features allow the orchestration workflow to safely spawn sub-agents, implement changes, and open PRs across many repositories with specific issue constraints.

What is the best way to scale GitHub bug fixes across repositories with many issues?

The best way to scale GitHub bug fixes is using parallel sub-agent orchestration. It automates issue triage, spawns fix agents based on filters, manages PRs, and handles reviews, effectively reducing manual toil for large repositories.

When should I not use automated sub-agents for GitHub issue fixes?

You should avoid using automated sub-agents for GitHub issue fixes when pre-flight safety checks fail or token resolution is incomplete. The workflow relies on curl-based GitHub REST API calls, so environments lacking proper API access are also unsuitable.