PR Triage

Evaluate external pull requests against a contribution rubric and assign triage labels.

6|2|Updated May 21, 2026
One-click install
npx skills add https://github.com/anajuliabit/aeon --skill pr-triage-anajuliabit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PR Triage
Source: https://github.com/anajuliabit/aeon/tree/main/skills/pr-triage
Command: npx skills add https://github.com/anajuliabit/aeon --skill pr-triage-anajuliabit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It prevents external pull requests from languishing unanswered by quickly producing a consistent first-touch verdict, rationale, and label so human reviewers can pick them up with clear context.

Core Features & Use Cases

  • Fast first-touch triage: Reads PR metadata and diff content, applies a structured rubric, and posts exactly one welcome comment that starts with Triage:.
  • Actionable labeling: Adds a single triage:* label (accepted / needs-changes / deferred / out-of-scope) to make queue filtering easy.
  • Idempotent state tracking: Avoids duplicate comments by checking memory/triaged-prs.json keyed on (PR number, headRefOid) and also defensively deduplicates by recent triage comments.

Quick Start

Use PR Triage to triage an opened external pull request by running the skill with an optional target like owner/repo#N or leaving it empty to triage all watched repositories.

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 external GitHub contributions?

Automate pull request triage by evaluating external PRs against a structured contribution rubric to instantly generate a verdict, welcome comment, and label. This provides consistent first-touch context so human reviewers can quickly pick up the queue.

Can I run automated code review workflows across all my watched GitHub repositories?

Automated code review workflows can run in single-PR, repo-wide, or fleet mode across watched GitHub repositories. The process focuses on open PRs from the last 14 days while skipping drafts, trusted authors, and already-triaged commits.

How does diff analysis handle out-of-scope changes in protected paths?

Diff analysis evaluates changes against contribution rubric rules and will conditionally close a PR if it detects out-of-scope protected-path violations. This enforces operational requirements and prevents unwanted modifications to critical code areas.

How do you prevent duplicate triage comments when automating GitHub PR reviews?

Prevent duplicate triage comments by using idempotent state tracking via a memory file keyed on PR number and head commit hash. The system also defensively deduplicates by checking for recent triage comments posted within the last 7 days.

What is the best way to evaluate PR originality and size before approving a code review?

Evaluate PR originality and size by applying an automated contribution rubric that checks scope, format, originality, and dimensions. This produces a structured first-touch verdict and rationale, ensuring clear context before human review.