A workflow for examining all open GitHub pull requests, grouping them, labeling them, and reviewing them one at a time.

Use it to list open pull requests, issues, labels, and recent merges; group related work; cross-reference issues; and guide decisions about comments and merging.

It turns a large, scattered list of pull requests into an organized queue with repository and issue context.

triage-prs — Command for Claude Code by EveryInc

About the project

Compound Engineering is a plugin that organizes software work into brainstorming, planning, implementation, review, and recording lessons for future changes. It is used with AI coding agents including Claude Code, Cursor, and Codex, and the catalogue entries provide parts of its agent, skill, command, and hook workflow.

EveryInc/compound-engineering-plugin · 25,543 stars · on GitHub · every.to

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin

Made for: Claude Code.

Or install compound-engineering, the plugin that ships this one along with the rest of its 37 skills, 1 command.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/everyinc/compound-engineering-plugin/triage-prs/github.svg)](https://agentmods.dev/commands/everyinc/compound-engineering-plugin/triage-prs)

Your own site

<a href="https://agentmods.dev/commands/everyinc/compound-engineering-plugin/triage-prs"><img src="https://agentmods.dev/badge/commands/everyinc/compound-engineering-plugin/triage-prs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/everyinc/compound-engineering-plugin/triage-prs"><img src="https://agentmods.dev/badge/commands/everyinc/compound-engineering-plugin/triage-prs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,620 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00024	$0.01620
Opus 5.5	$0.00010	$0.00648
Sonnet 5.5	$0.00005	$0.00324
Haiku 4.5	$0.00002	$0.00162

Measured 1mo ago against content hash 3b41fcab5d4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

triage-prs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

triage-prs — 100% identical, 0 lines differ
triage-prs — 100% identical, 0 lines differ
triage-prs — 100% identical, 2 lines differ
triage-prs — 91% identical, 18 lines differ

.claude/commands/triage-prs.md · 194 lines

How it starts

The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Triage Open Pull Requests

Review, label, and act on all open PRs for a repository using parallel review agents. Produces a grouped triage report, applies labels, cross-references with issues, and walks through each PR for merge/comment decisions.

Step 0: Detect Repository

Detect repo context:

Current repo: !gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "no repo detected"
Current branch: !git branch --show-current 2>/dev/null

If $ARGUMENTS contains a GitHub URL or owner/repo, use that instead. Confirm the repo with the user if ambiguous.

Step 1: Gather Context (Parallel)

Run these in parallel:

List all open PRs:

gh pr list --repo OWNER/REPO --state open --limit 50

List all open issues:

gh issue list --repo OWNER/REPO --state open --limit 50

List existing labels:

gh label list --repo OWNER/REPO --limit 50

Check recent merges (to detect duplicate/superseded PRs):
```
git log --oneline -20 main
```

Step 2: Batch PRs by Theme

Group PRs into review batches of 4-6 based on apparent type:

Bug fixes - titles with fix, bug, error descriptions
Features - titles with feat, add, new functionality
Documentation - titles with docs, readme, terminology
Configuration/Setup - titles with config, setup, install
Stale/Old - PRs older than 30 days

Step 3: Parallel Review (Team of Agents)

Spawn one review agent per batch using the Task tool. Each agent should:

For each PR in their batch:

Run gh pr view --repo OWNER/REPO <number> --json title,body,files,additions,deletions,author,createdAt
Run gh pr diff --repo OWNER/REPO <number> (pipe to head -200 for large diffs)
Determine:
- Description: 1-2 sentence summary of the change
- Label: Which existing repo label fits best
- Action: merge / request changes / close / needs discussion
- Related PRs: Any PRs in this or other batches that touch the same files or feature
- Quality notes: Code quality, test coverage, staleness concerns

Read the full file on GitHub · 194 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 194 lines · 24 tokens per session scan A 3b41fcab5d4c

Subscribe to this mod's changes

triage-prs is a command published in the GitHub repository EveryInc/compound-engineering-plugin (25,543 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 1,620 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Git and workflow compound engineering

triage-prs

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

Triage Open Pull Requests

Step 0: Detect Repository

Step 1: Gather Context (Parallel)

Step 2: Batch PRs by Theme

Step 3: Parallel Review (Team of Agents)

What this file has done since we first saw it

Other commands, from other repositories

speckit.git.validate

speckit.spex.submit

git

release-tag

repo-audit

advanced-code-review-context