Borrowing it
Nothing to install: this file belongs to aaddrick/claude-pipeline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aaddrick/claude-pipeline/main/.claude/skills/process-pr/SKILL.mdgit clone --depth 1 https://github.com/aaddrick/claude-pipelineWrote 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.
[](https://agentmods.dev/skills/aaddrick/claude-pipeline/process-pr)<a href="https://agentmods.dev/skills/aaddrick/claude-pipeline/process-pr"><img src="https://agentmods.dev/badge/skills/aaddrick/claude-pipeline/process-pr/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.
<a href="https://agentmods.dev/skills/aaddrick/claude-pipeline/process-pr"><img src="https://agentmods.dev/badge/skills/aaddrick/claude-pipeline/process-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00031 | $0.02814 |
| Opus 5.5 | $0.00012 | $0.01126 |
| Sonnet 5.5 | $0.00006 | $0.00563 |
| Haiku 4.5 | $0.00003 | $0.00281 |
Grade A, and why
process-pr 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process PR
Read PR review comments and act accordingly: if approved, create follow-up issues and merge; if changes requested, re-run implementation.
Announce at start: "Using process-pr to process PR #$1 for issue #$2"
Arguments:
$1— PR number (required)$2— Issue number that the PR addresses (required)$3— Base branch for re-implementation if needed (required)
Examples:
/process-pr 142 130 aw-next/process-pr 456 123 main
Process
digraph process_pr {
rankdir=TB;
node [shape=box];
validate [label="1. Validate inputs"];
fetch [label="2. Fetch PR & review comments"];
check [label="3. Check review status"];
approved [label="Approved path"];
changes [label="Changes requested path"];
merge [label="4a. Squash merge PR"];
comment [label="4b. Comment on issue"];
close [label="4c. Close issue"];
delete [label="4d. Delete branch"];
parse [label="4e. Parse comments for follow-ups"];
create_issues [label="4f. Create follow-up issues"];
rerun [label="5. Re-run /implement-issue"];
output_success [label="Output: Success summary"];
output_rerun [label="Output: Re-implementation started"];
validate -> fetch -> check;
check -> approved [label="approved"];
check -> changes [label="changes requested"];
approved -> merge -> comment -> close -> delete -> parse -> create_issues -> output_success;
changes -> rerun -> output_rerun;
}
Why merge first: Follow-up issues should only be created if the merge succeeds. Creating issues before merge can leave orphaned issues if merge fails (conflict, permissions, etc.). Merging first ensures we only create follow-ups for work that actually landed.
Step 1: Validate Inputs
# Verify PR exists and is open
gh pr view $PR_NUMBER --json state,number,title,headRefName,reviews
# Verify issue exists and is open
gh issue view $ISSUE_NUMBER --json state,number,title
If validation fails: Stop and report error.
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.
- 2mo ago First seen · 444 lines · 31 tokens per session scan A f00094bff7c5
process-pr is a skill published in the GitHub repository aaddrick/claude-pipeline (130 stars, last pushed 8mo ago), licensed MIT. It adds 31 tokens to every session and 2,814 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.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…