PR Triage

Triages external GitHub pull requests with a rubric verdict, label, and comment.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon-bd --skill pr-triage-aaronjmars
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: PR Triage
Source: https://github.com/aaronjmars/aeon-bd/tree/main/skills/pr-triage
Command: npx skills add https://github.com/aaronjmars/aeon-bd --skill pr-triage-aaronjmars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? External pull requests that sit unanswered make a project look unwelcoming, and maintainers waste time re-reading every new PR from scratch. This Skill provides first-touch triage within minutes of a PR opening: it reads the diff, applies a structured rubric, posts a verdict comment, and labels the PR so a human reviewer picks it up with full context. ## Core Features & Use Cases - Structured rubric verdicts: Scores each PR on scope, format, originality, and size, then assigns ACCEPTED, NEEDS-CHANGES, DEFER, or OUT-OF-SCOPE. - Automated labeling and comments: Posts exactly one **Triage:** comment per PR commit and applies a triage:* namespace label, with idempotency keyed on PR number and head SHA. - Fleet or single-PR modes: Scans all watched repos from memory/watched-repos.md, a single repo, or one specific PR, with a budget of 8 PRs per repo per run. - Use Case: A maintainer of several open-source repos wakes up to find every external PR opened overnight already triaged — welcomed contributors have actionable feedback, out-of-scope workflow changes are closed with a redirect to issues, and first-time contributors are flagged for a personal welcome. ## Quick Start Run the PR triage skill on owner/repo to scan open external pull requests and post verdict comments with labels.

Frequently Asked Questions about PR Triage

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

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

Run the triage workflow with a target like owner/repo or owner/repo#N, or leave it empty to scan all watched repos. It fetches open PRs via the gh CLI, skips drafts and trusted authors, applies a rubric, and posts a verdict comment plus a triage label.

What criteria does automated PR triage use to accept or reject contributions?▼

The rubric checks four things: scope (only allowed paths touched), format (SKILL.md frontmatter completeness), originality (no skill name collisions on main), and size (under 500 changed lines). Verdicts are ACCEPTED, NEEDS-CHANGES, DEFER, or OUT-OF-SCOPE, with first match winning.

Does PR triage work with draft or bot-authored pull requests?▼

No. Draft PRs, WIP-titled PRs, PRs with blocking labels, and PRs from bot logins ending in [bot] are skipped. Trusted authors listed in the watched-repos memory file are also excluded from triage.

Will automated triage close my pull request?▼

Only OUT-OF-SCOPE verdicts with unambiguous protected-path violations, such as changes to .github/workflows/ or the root binary, are closed as not planned. ACCEPTED, NEEDS-CHANGES, and DEFER verdicts never close a PR.

How does PR triage avoid posting duplicate comments?▼

Idempotency is keyed on the PR number and headRefOid stored in a JSON state file, so an unchanged head commit is never re-triaged. A defensive fallback also checks for an existing Triage comment posted within the last 7 days.