PR Triage

Triage external GitHub pull requests with rubric verdicts and labels.

626|225|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --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/tree/main/skills/pr-triage
Command: npx skills add https://github.com/aaronjmars/aeon --skill pr-triage-aaronjmars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents unanswered external pull requests from lingering without context by automatically triaging them within minutes and guiding maintainers on what to do next.

Core Features & Use Cases

  • Automated first-touch triage: Reviews the PR diff and applies a structured rubric to determine scope, format, originality, and size suitability.
  • Consistent contributor communication: Posts exactly one welcoming comment starting with Triage: that explains the verdict and next actions when relevant.
  • Actionable labeling: Adds a single triage:* label so humans can quickly filter and pick up the PR at the right workflow stage.
  • Idempotent re-triage behavior: Tracks (PR number, headRefOid) to avoid duplicate comments and labels while still allowing re-triage on new pushes.

Quick Start

Ask Aeon to run PR Triage for a specific pull request like owner/repo#123 to get a verdict comment and the corresponding triage label automatically.

Frequently Asked Questions about PR Triage

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

FAQPage Schema
How do I automate pull request triage for newly opened external GitHub PRs?

Automated pull request triage reviews the PR diff using a structured rubric to determine scope, format, originality, and size. It then posts a standardized welcoming comment and applies a matching triage label to guide maintainers on next actions.

How does the triage agent handle draft pull requests or trusted authors?

The triage agent applies skip rules to bypass draft pull requests, trusted authors, and PRs that are already labeled or triaged. This ensures automated first-touch handling only targets newly opened external PRs requiring review.

Can I run automated PR triage across a fleet of watched GitHub repositories?

Yes, automated PR triage supports fast first-touch handling across one repo, a single PR, or a fleet of watched repos. It fetches GitHub PR diffs and generates rubric-based verdicts with matching labels for each.

What prevents duplicate triage comments when a contributor pushes new commits?

Idempotent re-triage behavior tracks the PR number and headRefOid in a triaged-prs state. This prevents duplicate comments and labels on unchanged branches while allowing automatic re-triage when a new push changes the headRefOid.

What is the best way to add consistent labeling and welcoming comments for external contributors?

Rubric-based PR triage adds a single triage label and posts exactly one welcoming comment starting with Triage. This provides consistent contributor communication and actionable filtering for maintainers across the code review workflow.

Does automated PR triage require manual configuration of the diff rubric criteria?

Automated PR triage uses a built-in structured rubric to evaluate diff scope, format, originality, and size suitability. It produces a standardized verdict and matching label without requiring manual rubric configuration for each repository.