github-pr-triage

Triage GitHub pull requests with parallel background analysis and conservative auto-close.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/gabrielnsmnto/kord-aios --skill github-pr-triage-gabrielnsmnto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-triage
Source: https://github.com/gabrielnsmnto/kord-aios/tree/main/.opencode/skills/github-pr-triage
Command: npx skills add https://github.com/gabrielnsmnto/kord-aios --skill github-pr-triage-gabrielnsmnto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires typer, rich, and includes scripts (resource) components.

What problem does it solve? Repositories accumulate open pull requests faster than maintainers can review them, leaving stale, duplicate, or merge-ready PRs unaddressed. This Skill automates the full triage cycle: fetching every open PR, analyzing each one in an isolated background task, and producing actionable recommendations. ## Core Features & Use Cases - Exhaustive PR Collection: Uses the bundled gh_fetch.py script with pagination to retrieve every open PR via the GitHub CLI, with optional time-based filtering. - Parallel Streaming Analysis: Launches one independent background task per PR and streams categorized results (merge-ready, needs review, stale, draft, close-eligible) in real time as each task completes. - Conservative Auto-Close: Closes only PRs that clearly qualify (already implemented, already fixed, outdated direction, or abandoned), with friendly close comments and confirmation. - Use Case: A maintainer facing 50 open PRs runs the triage, watches live progress as each PR is categorized, auto-closes 8 obsolete PRs, and receives a final report listing 5 PRs ready to merge immediately. ## Quick Start Ask the agent to triage all open PRs in the current repository and stream the analysis results as each one completes.

Frequently Asked Questions about github-pr-triage

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

FAQPage Schema
How do I triage open GitHub pull requests automatically?▼

Run the triage workflow, which fetches every open PR with the gh CLI, launches one background analysis task per PR, and streams categorized results. It ends with a report grouping PRs into merge-ready, needs review, stale, draft, and close-eligible buckets.

How to fetch all GitHub PRs with pagination using gh CLI?▼

Use the bundled gh_fetch.py script with the prs command, which paginates in batches of 500 using created-date search filters until no more results return. It supports JSON, table, or count output and optional time-based filtering.

Does the PR triage auto-close pull requests without confirmation?▼

No, auto-close is conservative and asks for confirmation unless the user explicitly approved auto-closing. It only closes PRs that are already implemented, already fixed, outdated, or abandoned for over six months, always with a friendly comment.

What criteria determine if a GitHub PR is ready to merge?▼

A PR is merge-ready when it has approvals, passing CI, no conflicts, and is not a draft. The analysis also checks project alignment, branch existence, and whether the changes were already implemented on the base branch.

Why analyze each PR in a separate background task?▼

Isolating each PR in its own background task prevents one failure from blocking others, enables parallel execution for speed, and allows results to stream to the user in real time as each analysis completes.