PR Triage

Classify open GitHub Pull Requests into predefined categories via the GitHub API.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/jimmymalhan/codereview-pilot --skill pr-triage-jimmymalhan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PR Triage
Source: https://github.com/jimmymalhan/codereview-pilot/tree/main/.claude/skills/pr-triage
Command: npx skills add https://github.com/jimmymalhan/codereview-pilot --skill pr-triage-jimmymalhan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the classification and management of open Pull Requests (PRs), ensuring that PRs are correctly categorized, linked to project goals, and that stale or duplicate PRs are identified for closure.

Core Features & Use Cases

  • PR Classification: Assigns one of seven categories (keep, merge-ready, needs-update, duplicate, stale, superseded, close-if-permitted) to each open PR.
  • Roadmap Linking: Identifies PRs missing links to roadmap items and suggests or adds them.
  • Stale/Duplicate Detection: Flags PRs that haven't been updated in 7+ days or appear to be duplicates of existing PRs.
  • Use Case: Automatically triage all open PRs in a repository, flagging those that need updates from the author, identifying duplicates, and preparing stale PRs for archival.

Quick Start

Run the PR Triage skill to classify all open pull requests.

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 my GitHub repository?

Automating pull request triage involves classifying open GitHub PRs into predefined categories to streamline review workflows. This Skill queries the GitHub API for open and closed PRs, analyzing branch hygiene data to categorize them as merge-ready, stale, or duplicate.

What is the best way to identify duplicate or stale GitHub pull requests automatically?

Identifying stale or duplicate pull requests automatically is done by analyzing PR branch hygiene data against existing open and closed PRs. The Skill flags PRs inactive for 7+ days as stale and matches patterns to find duplicates for potential closure.

Can I automatically categorize open pull requests to streamline code review workflows?

Yes, you can categorize open pull requests to streamline code review workflows by assigning one of seven categories: keep, merge-ready, needs-update, duplicate, stale, superseded, or close-if-permitted. This classification helps reviewers prioritize PRs needing immediate attention.

How does PR classification link pull requests to roadmap items?

PR classification links pull requests to roadmap items by identifying open PRs missing these connections and suggesting or adding the appropriate links. This ensures all active PRs are aligned with defined project goals during the triage process.

Do I need any external dependencies to run automated PR triage on my repository?

No external dependencies are required to run automated PR triage on your repository. The Skill operates independently using internal scripts and references to query the GitHub API and analyze branch hygiene data directly.

When should I use automated PR triage instead of manual code review categorization?

Automated PR triage should be used when managing repositories with numerous open pull requests exceeding manual review capacity. It is ideal for identifying PRs needing author updates, detecting duplicates, and preparing stale PRs for archival efficiently.