gh-issues

Automate GitHub issue triage, fix agent spawning, and PR creation via parallel sub-agents.

7|12|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/borealBytes/my-farm-advisor --skill gh-issues-borealbytes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issues
Source: https://github.com/borealBytes/my-farm-advisor/tree/main/skills/gh-issues
Command: npx skills add https://github.com/borealBytes/my-farm-advisor --skill gh-issues-borealbytes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates automatic GitHub issue handling by fetching issues, spawning parallel sub-agents to implement fixes, and monitoring PR reviews to close the loop.

Core Features & Use Cases

  • Fetches issues for a given owner/repo and filters by labels, milestones, and assignees
  • Spawns parallel sub-agents to implement fixes and open PRs, then monitors PR reviews for feedback
  • Supports fork mode, watch intervals, model selection, and optional Telegram notifications for summaries

Quick Start

Run /gh-issues with a target owner/repo to begin automatic issue triage and fix workflows.

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 resolution and pull request creation?

Automate GitHub issue resolution by spawning parallel sub-agents to implement fixes and open PRs. The workflow fetches target issues, concurrently processes fixes, and monitors pull request reviews to close the loop.

Can I filter GitHub issues by labels and milestones before spawning fix agents?

Yes, you can filter GitHub issues by labels, milestones, and assignees before spawning sub-agents. The automation applies these filters to your owner/repo workflows to triage relevant items concurrently.

Does GitHub issue automation support fork mode and watch intervals?

Yes, GitHub issue automation supports fork mode, configurable watch intervals, and model selection for sub-agents. These features ensure flexible workflow orchestration and continuous monitoring of PR reviews.

What is the best way to manage concurrent sub-agents fixing GitHub issues?

The best way to manage concurrent sub-agents is using an orchestrator that handles token resolution, pre-flight checks, and concurrent spawning. It collects results with safety checks and error handling for reliable automation.

How do I get summary notifications for automated GitHub issue workflows?

Get summary notifications for automated GitHub issue workflows via optional Telegram notifications. The orchestrator sends these summaries after fetching issues, spawning sub-agents, and monitoring resulting PR reviews.

Why does automated GitHub issue processing fail during sub-agent spawning?

Automated GitHub issue processing fails during sub-agent spawning due to invalid token resolution or failed pre-flight checks. The orchestrator implements safety checks and error handling to manage these concurrent execution failures.