gh-issues

Automate GitHub issue triage and remediation with parallel sub-agents.

3.2k|259|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/nexu-io/nexu --skill gh-issues-nexu-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issues
Source: https://github.com/nexu-io/nexu/tree/main/apps/desktop/static/bundled-skills/gh-issues
Command: npx skills add https://github.com/nexu-io/nexu --skill gh-issues-nexu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issues are triaged and resolved by launching parallel sub-agents that implement fixes and open PRs, then monitor reviews.

Core Features & Use Cases

  • Spawn multiple focused agents to diagnose, patch, and PR code across source and fork repos.
  • Support labels, milestones, assignees, and watch/cron workflows to automate ongoing maintenance.
  • Use case: when a team needs automated fixes and PRs across several issues with consistent review handling.

Quick Start

Invoke the gh-issues skill with a target repository in the format /gh-issues owner/repo to begin processing.

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 issues at once?

Automating GitHub issue triage is done by spawning parallel sub-agents that diagnose code, implement patches, and open PRs across source and fork repositories automatically.

Can I use cron schedules to monitor and fix GitHub issues automatically?

Yes, GitHub issue remediation supports cron schedules and watch workflows to automate ongoing maintenance, allowing agents to continuously monitor and resolve new issues.

How do I filter which GitHub issues get automated fixes and PRs?

Automated issue remediation supports filtering by labels, milestones, and assignees, ensuring sub-agents only process and open PRs for issues matching your specific criteria.

What is the best way to auto-fix GitHub issues across forked repositories?

Auto-fixing GitHub issues across forks is handled by parallel sub-agents that implement fixes and create pull requests, operating seamlessly across both source and forked repos.

Do I need a GitHub token to automate issue remediation and open pull requests?

Yes, automating issue fixes and creating PRs requires a provided GH_TOKEN to authenticate GitHub REST API requests via curl for repository operations and status checks.

How do I notify channels when automated GitHub issue fixes are completed?

Notifying channels of completed fixes is supported through built-in notification options, which alert your team after sub-agents finish implementing patches and opening PRs.