pr-triage

Audit open GitHub pull requests to classify size, detect overlaps, and flag staleness.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Alamator/code-ultimate --skill pr-triage-alamator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-triage
Source: https://github.com/Alamator/code-ultimate/tree/main/examples/skills/pr-triage
Command: npx skills add https://github.com/Alamator/code-ultimate --skill pr-triage-alamator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers and reviewers face time-consuming manual triage of open pull requests, missed overlaps, stale PRs, and inconsistent review workflows. This Skill provides a repeatable, audit-first workflow that classifies PRs, highlights risks, and prepares validated review drafts so maintainers can act efficiently.

Core Features & Use Cases

  • Phase 1 — Audit: Collects PR metadata, classifies size and CI status, detects overlaps and clusters, and produces a triage table with actionable recommendations.
  • Phase 2 — Deep Review: Optionally spawns parallel code-reviewer agents to generate structured, file/line-specific review reports and aggregates the results.
  • Phase 3 — Comment Drafting: Generates English review comment drafts from templates and requests explicit user validation before posting.
  • Phase 4 — Worktree Setup: Optionally creates local git worktrees per PR for hands-on testing, with safeguards for cache, .gitignore, and fetch failures.
  • Use Cases: Catch up after a backlog of >5 PRs, focus on specific PR numbers, handle problematic PRs (large, CI failures, merge conflicts), or prepare local review environments.

Quick Start

Run the pr-triage skill to audit open PRs, generate a triage table, and draft validated review comments for selected 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 triaging open GitHub pull requests to detect stale PRs and overlaps?

To triage open GitHub pull requests, the Skill fetches PR metadata and diffs, classifies PR size, detects overlapping changes, flags stale PRs, and generates a triage table with actionable recommendations for maintainers.

What is the best way to draft and validate GitHub PR review comments before posting?

The best way to draft GitHub PR review comments is to generate them from templates using a dedicated comment drafting phase, which requires explicit user validation before any comment is posted to the pull request.

Do I need gh CLI authentication to review pull requests and fetch PR diffs?

Yes, you need gh CLI authentication to review pull requests and fetch PR diffs. The Skill requires gh CLI authentication and git worktree support to pull metadata and optionally create local review environments.

Can I use parallel code-reviewer agents for deep pull request reviews?

Yes, you can use parallel code-reviewer agents for deep pull request reviews. The Skill optionally spawns parallel agents to generate structured, file and line-specific review reports, with sequential fallbacks if agents fail.

How do I set up local git worktrees per PR for hands-on testing and review?

To set up local git worktrees per PR, the Skill optionally creates worktrees with built-in safeguards for cache, .gitignore, and fetch failures, enabling maintainers to prepare local hands-on testing environments for selected pull requests.