PR Triage

Automate triage and labeling of external GitHub pull requests.

Updated Jul 16, 2026

Search Tags:#automation #pull request #github #review #triage

Ready to run

npx skills add https://github.com/enuno/noesis-aeon --skill pr-triage-enuno

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: PR Triage
Source: https://github.com/enuno/noesis-aeon/tree/main/skills/pr-triage
Command: npx skills add https://github.com/enuno/noesis-aeon --skill pr-triage-enuno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the initial review of external pull requests, reducing the time to respond and improving the first impression for contributors.

Core Features & Use Cases

Automated Triage: Applies a structured rubric to determine the status of external pull requests.
Comment and Labeling: Posts a comment with a verdict and rationale, and applies a label for further review.
Use Case: For organizations with a high volume of external pull requests, this Skill helps maintain a welcoming environment by quickly addressing new contributions.

Quick Start

Run the PR Triage Skill to automatically triage and label new pull requests in your repository.

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?▼

Automating pull request triage requires applying a structured rubric to evaluate external GitHub contributions, determine their status, post a verdict comment, and apply labels. This reduces response time and improves the contributor experience.

What is the best way to apply first-touch review labels to new pull requests?▼

First-touch review labels are applied by evaluating new pull requests against a structured rubric to determine acceptance, needed changes, deferment, or out-of-scope status, then automatically posting a comment with the verdict and rationale.

How does automated triage determine if an external pull request is out of scope?▼

Automated triage determines if a pull request is out of scope by applying a structured rubric that evaluates the contribution's status, categorizing it as accepted, needing changes, deferred, or out of scope, then posting the verdict as a comment.

Do I need GitHub API access to automate pull request labeling?▼

Yes, GitHub API access is required to automate pull request labeling. You must also configure watched repositories and identify trusted authors so the automated triage system can evaluate external contributions and apply appropriate status labels.

Can I use automated triage for repositories with a high volume of external pull requests?▼

Yes, automated triage is designed for organizations with a high volume of external pull requests. It helps maintain a welcoming environment by quickly addressing new contributions with structured rubric evaluations and automated labeling.

What are the limitations of automated pull request triage?▼

Automated pull request triage is limited to evaluating external contributions based on a configured rubric, watched repositories, and trusted authors. It does not replace human review but provides initial status verdicts and labeling for further action.