github-issue-triage

Name: github-issue-triage
Availability: InStock
Author: aniwei

Automate GitHub issue triage with per-issue background agents and structured reports.

Updated Feb 3, 2026

Search Tags:#automation #GitHub #parallel #issues #triage #pagination #report

Ready to run

npx skills add https://github.com/aniwei/vitamin-code --skill github-issue-triage-aniwei

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-issue-triage
Source: https://github.com/aniwei/vitamin-code/tree/main/refs/oh-my-opencode/.opencode/skills/github-issue-triage
Command: npx skills add https://github.com/aniwei/vitamin-code --skill github-issue-triage-aniwei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub Issue Triage Specialist automates exhaustive collection of issues within a given time window, spawns a dedicated background agent per issue, and compiles a comprehensive triage report. It ensures no issues are missed by exhaustively paginating results and correlates related pull requests and discussion activity to assess relevance and status.

Core Features & Use Cases

Exhaustive pagination to fetch all issues in a repo within a time window.
One background agent per issue for parallel analysis.
Generates a comprehensive triage report including type, project validity, status, and linked PRs.
Triggers: 'triage issues', 'analyze issues', 'issue report'.

Quick Start

Identify repository: use gh repo view --json nameWithOwner -q .nameWithOwner to determine owner/repo, or set REPO manually.
Define a time window (default: 48 hours) and run exhaustive pagination for issues and PRs.
Launch 1 background agent per issue to analyze concurrently.
Collect all results and generate a categorized triage report ready for action.

Frequently Asked Questions about github-issue-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate GitHub issue triage for a busy repository?▼

Automate GitHub issue triage by using this Skill to exhaustively paginate issues within a time window and spawn a dedicated background agent per issue for parallel analysis. It evaluates issue type, validity, status, and engagement, then outputs a structured report for maintainer action.

What is the best way to analyze GitHub issues and linked PRs in parallel?▼

The best way to analyze GitHub issues in parallel is spawning a background agent per issue. This Skill concurrently evaluates all issues within a time window, correlates related pull requests and discussion activity, and compiles a categorized triage report.

Do I need the GitHub CLI to generate an issue triage report?▼

Yes, you need the GitHub CLI (gh) and appropriate permissions to use this Skill. It relies on the CLI to exhaustively fetch repository issues, linked PRs, and comments before spawning background agents to analyze them.

Can I triage GitHub issues from a specific time window?▼

Yes, you can triage GitHub issues from a specific time window. The Skill defaults to a 48-hour window but allows you to define a custom timeframe to ensure all relevant issues are exhaustively paginated and analyzed.

How does parallel issue analysis handle large repositories with many open issues?▼

Parallel issue analysis handles large repositories by exhaustively paginating all issues within the specified time window and launching one background agent per issue. This ensures no issues are missed and assesses project validity and engagement for a scalable triage workflow.

What does a structured GitHub issue triage report include?▼

A structured GitHub issue triage report includes the issue type, project validity, current status, and linked PRs. It compiles these results from the parallel background agents to provide categorized, actionable insights for maintainers.