triage-github

Triage open GitHub issues, PRs, and discussions with parallel subagents into a prioritized report.

3.1k|316|Updated Oct 8, 2025
One-click install
npx skills add https://github.com/TanStack/ai --skill triage-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-github
Source: https://github.com/TanStack/ai/tree/main/.grok/skills/triage-github
Command: npx skills add https://github.com/TanStack/ai --skill triage-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers of active repositories struggle to decide which open PRs to review first, which issues to fix first, and which discussions need attention. This Skill bulk-evaluates every open item on a GitHub repository and produces a single prioritized report.

Core Features & Use Cases

  • Parallel triage at scale: Fans out up to 100 subagents (one per PR, issue, or discussion) that each fetch details via the gh CLI and return a structured JSON verdict with priority (P0–P3) and a recommended action.
  • Linkage and dedup: Folds issues closed by an open PR under that PR, and discussions already tracked by an issue or PR under their tracker, so each unit of work appears exactly once.
  • Run-over-run deltas: Writes a dated JSON snapshot per run and diffs against the previous one to surface new, resolved, escalated, de-escalated, and recurring high-priority items.
  • Use Case: A maintainer returning from vacation asks to "triage the backlog" and receives a TRIAGE_REPORT.md ranking P0 PRs to merge today, bugs to fix this sprint, and unanswered Q&A discussions needing a response.

Quick Start

Ask the assistant to triage all open issues, PRs, and discussions in the current repository and produce a prioritized report of what to review first.

Frequently Asked Questions about triage-github

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

FAQPage Schema
How do I triage open GitHub issues and PRs in bulk?

Run this Skill from inside the repository with an authenticated gh CLI. It fetches all open PRs, issues, and discussions, fans out one subagent per item to score priority, and writes a ranked TRIAGE_REPORT.md.

How does the triage prioritize pull requests and issues?

Each item is scored P0 through P3 using rubrics based on CI status, review state, mergeability, reactions, comments, and age. PRs rank above the issues they close, and issues rank above discussions they track, so work appears once.

Does this work on repositories with GitHub Discussions disabled?

Yes. The Skill checks hasDiscussionsEnabled via gh repo view first. If discussions are disabled, it skips fetching them entirely and notes in the report that the section was omitted.

What happens when a repository has more than 100 open items?

The Skill caps triage at 100 items total. It asks whether to cap at the 100 most recently updated or split into batches, prioritizing PRs first, then issues, then discussions, and lists skipped items in the report.

Can the triage skill close issues or merge PRs automatically?

No. The Skill is strictly read-only and never closes issues, merges PRs, or posts comments. The only outward action is publishing the report as a secret gist, and only after explicit user approval each run.

How does the report show what changed since the last triage?

Each run writes a dated JSON snapshot to .agent/triage/ or .triage/. The next run diffs against the most recent prior snapshot to report new, resolved, escalated, de-escalated, and recurring high-priority items.