pr-review
Skill7 starsChanged 49 days agoMITView on GitHub
PR triage and merge: lists open PRs, summarizes diffs and review state, merges one PR at a time with an explicit gate. Part of the governance pack: inert until docs/GOVERNANCE.md is adopted, and needs an authenticated gh. Use when the operator says: pr review, /pr-review, review pr, open prs, merge pr.
195 other projects use a version of this.
Adopted by
Most recently taken up by
- neomjs/neo-agent-skillstheir own version, first seen Nov 15, 2026
- asarelcastellanos/claude-workbenchtheir own version, first seen Nov 15, 2026
- ceilidhboy/skillstheir own version, first seen Nov 15, 2026
- NVIDIA/cclustertheir own version, first seen Nov 15, 2026
- jellydn/my-ai-toolstheir own version, first seen Nov 15, 2026
- richkuo/rk-skillstheir own version, first seen Nov 14, 2026
Used with
Projects with it also use oss-pr, pr-automation and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CES-LtdSkilloss-pr
Use when creating a pull request, after committing changes, or when user invokes /oss-pr. Covers branch management, quality checks, commit, push, and PR creation.
Also in 3 projects that use this
CES-LtdSkillpr-automation
PR Automation Orchestrator: poll open PRs, check CI, run review, fix, and merge eligible PRs. Use when: (1) Invoked by daemon via scripts/pr-automation.sh, (2) User says "/pr-automation".
Also in 3 projects that use this
jtenniswoodSkillexpert-reset
Reimagine this repository from first principles using the current product and user experience as the target. Use when the user says "/expert-reset", asks how the project should be rebuilt if starting again, wants bold architecture or component-structure recommendations, or wants a research-only reset plan unconstrained by current implementation details.
Also in 3 projects that use this
jtenniswoodSkillupdates
Summarize user-facing project updates from the last 7 days, ordered by importance and written as one-sentence "Feature: description" entries. Use when the user says "/updates", asks what changed recently, or wants a concise list of recent features, device support, fixes that users will notice, or other product value.
Also in 3 projects that use this
openchamberSkillclack-cli-patterns
Use when creating or modifying OpenChamber CLI commands, prompts, terminal output, non-TTY behavior, `--quiet`, or `--json` behavior.
Also in 3 projects that use this
openchamberSkilldrag-to-reorder
Use when implementing or modifying OpenChamber sortable or drag-to-reorder behavior, especially `@dnd-kit`, touch/mobile interactions, variable-width items, or wrapping layouts.
Also in 3 projects that use this
- +6 more from openchamber
Other versions195 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 195
- Significant-Gravitas/AutoGPT★ 188ksame name
- pytorch/pytorch★ 106ksame name
- rtk-ai/rtk★ 87ksame name
- saadeghi/daisyui★ 43ksame name
- rustfs/rustfs★ 36ksame name
- dotnet/maui★ 23ksame name
- NVIDIA/Megatron-LM★ 18ksame name
- MiniMax-AI/skills★ 14ksame name
- openchamber/openchamber★ 13ksame name
- btriapitsyn/openchamber★ 13ksame name
185 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- daily-log/CLAUDE.mdCLAUDE.md
- memory/CLAUDE.mdCLAUDE.md
- operators/CLAUDE.mdCLAUDE.md
- daily-briefingSkill
- handoverSkill
- html-previewSkill
- meeting-debriefSkill
- memory-checkupSkill
- session-debriefSkill
- setup-company-brainSkill
- shipSkill
- skill-detectorSkill
- skill-improveSkill
- sparringSkill
- syncSkill
- system-checkupSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 5 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 179 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 20
Run gh auth status. If it fails, say this skill needs an authenticated gh CLI, point at the dependency matrix in the README, and stop.
- Very specific: line 60
If the diff is longer than 500 lines, show the first 200 and the last 100 lines with a [ … skipped … ] marker between them, instead of the …
- Very specific: line 65
If .github/CODEOWNERS exists in the repo, map the changed files (from Step 1) against it and tell the operator whose review the PR is …
- Very specific: line 71
If .github/CODEOWNERS does not exist, skip this step silently: CODEOWNERS is opt-in, its absence is a normal, unconfigured state.
- Distinctive: line 86
Before running anything, show the exact command that will run and what it does (PR number, squash, branch deletion, target branch), then …
- Very specific: line 91
Proposal gate: If the head branch is a proposal (*/proposals-*), checks run before anything else, all read from the registry, never from a …
- Very specific: line 122
If the PR's head branch (headRefName from Step 1) is checked out in a local worktree, remove the worktree first, or the local branch …
- Distinctive: line 158
Always show the diff before offering merge.
- Distinctive: line 162
Never close someone else's PR without asking first.
- Distinctive: line 164
Never force anything: no force-push, no bypassing branch protection.
- Distinctive: line 165
If branch protection requires reviews the PR doesn't have, the merge fails.
“Common” is measured: kept by at least 6 in 10 of the 179 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
pr-review
PR triage and merge. Lists open pull requests, summarizes one on request, and
merges through an explicit confirmation gate. This is one of the three
governance-pack steps in docs/GOVERNANCE.md: it does nothing until a repo
admin has activated feature branches (step 2) or CODEOWNERS (step 3) there,
and it needs the gh CLI authenticated against the repo.
Precondition
Run gh auth status. If it fails, say this skill needs an authenticated gh
CLI, point at the dependency matrix in the README, and stop. Do not attempt
any of the steps below without it.
Mode A: no argument, list and summarize
gh pr list --state open --json number,title,author,createdAt,reviewDecision,mergeStateStatus,headRefNameFor each PR, show one line: number, title, author, age (from createdAt),
review decision (APPROVED, CHANGES_REQUESTED, or none), merge state
(CLEAN, BLOCKED, BEHIND, DIRTY). Highlight any PR whose merge state is
blocked or dirty.
A PR whose headRefName matches */proposals-* is a proposal: a non-owner's
change on a sensitive path, waiting for a sensitive owner (docs/GOVERNANCE.md
step 3). List proposals first, prefixed [proposal], and say who they are
waiting on: teams usually agree a turnaround for proposals, often the same day,
and a proposal that has aged past it is the first finding of this run.
Close with: "Pick a PR number to focus on, or call /pr-review <n> directly."
Mode B: /pr-review <n>, focus on one PR
Step 1: Header
gh pr view <n> --json title,author,baseRefName,headRefName,state,mergeStateStatus,reviewDecision,statusCheckRollup,filesShow title, author, base and head branch, state, merge status, review decision, status checks, and the list of changed files.
Step 2: Diff
gh pr diff <n>If the diff is longer than 500 lines, show the first 200 and the last 100
lines with a [ … skipped … ] marker between them, instead of the full diff.
Step 3: Map the scope (if CODEOWNERS exists)
If .github/CODEOWNERS exists in the repo, map the changed files (from
Step 1) against it and tell the operator whose review the PR is routed to.
Per docs/GOVERNANCE.md step 3, CODEOWNERS is a map, not enforcement: it
tells you who GitHub will request as a reviewer, it does not by itself block
or allow a merge. State it that way, don't imply the file is a gate.
If .github/CODEOWNERS does not exist, skip this step silently: CODEOWNERS
is opt-in, its absence is a normal, unconfigured state.
Step 4: Ask for action
Offer exactly these options, nothing more:
merge: squash-merge and delete the branchcomment <text>: leave a review comment,gh pr comment <n> --body "<text>"request-changes <text>: request changes formally,gh pr review <n> --request-changes --body "<text>"close: close without merging,gh pr close <n>skip: exit without taking any action
Merge gate
Before running anything, show the exact command that will run and what it does (PR number, squash, branch deletion, target branch), then wait for a pointed "ok". Never merge on momentum carried over from earlier in the conversation: an earlier "yes let's merge that" is not this gate.
Proposal gate. If the head branch is a proposal (*/proposals-*), checks run
before anything else, all read from the registry, never from a name written here:
HEAD_REF=$(gh pr view <n> --json headRefName -q .headRefName)
case "$HEAD_REF" in
*/proposals-*)
ME_SLUG=$(scripts/lib/operator-registry.sh resolve) || exit 1
ME_LOGIN=$(scripts/lib/operator-registry.sh field "$ME_SLUG" github | sed 's/^@//' | tr '[:upper:]' '[:lower:]')
AUTHOR=$(gh pr view <n> --json author -q .author.login | tr '[:upper:]' '[:lower:]')
if [ -z "$AUTHOR" ]; then
echo "PROPOSAL GATE: the pull request's author could not be read; the gate cannot be evaluated."
exit 1
fi
if [ "$AUTHOR" = "$ME_LOGIN" ]; then
echo "PROPOSAL GATE: you opened this proposal; a sensitive owner merges it, never the proposer."
exit 1
fi
if ! scripts/lib/operator-registry.sh is-sensitive-owner "$ME_SLUG"; then
echo "PROPOSAL GATE: operators/$ME_SLUG.md does not declare sensitive_owner: true; only a sensitive owner merges a proposal."
exit 1
fi
;;
esacOn any PROPOSAL GATE line, stop and show it. Do not offer merge for that PR;
comment, request-changes, close (own proposal only, with a reason) and skip
stay available. On an IDENTITY ERROR from the registry, stop as well: the rule in
operators/CLAUDE.md is binding here too.
If the PR's head branch (headRefName from Step 1) is checked out in a local
worktree, remove the worktree first, or the local branch deletion below
fails:
HEAD_REF=$(gh pr view <n> --json headRefName -q .headRefName)
# The porcelain listing prints, per worktree, a "worktree <path>" line, a HEAD
# line, then "branch refs/heads/<name>": the path sits two lines above the match.
WT_PATH=$(git worktree list --porcelain | grep -B2 -Fx "branch refs/heads/$HEAD_REF" | grep "^worktree " | cut -d" " -f2-)
[ -n "$WT_PATH" ] && git worktree remove "$WT_PATH"Then, once the operator has given the pointed "ok":
gh pr merge <n> --squash --delete-branchSquash keeps linear history, matching docs/GOVERNANCE.md step 1. There is
no --admin flag here: if branch protection on the repo requires reviews
that this PR does not have, the merge simply fails until the review exists.
Report that outcome honestly, don't look for a way around it.
Post-merge
git fetch origin main --quietThat's the only post-merge step. Never checkout or pull here: the local
working tree may hold uncommitted work from an in-progress session, and a
fetch only refreshes the remote-tracking ref without touching the tree.
Local main realigns on its own at the next /sync or debrief.
Rules
- Always show the diff before offering merge. Never merge blind.
- One PR at a time. No bulk merges.
- A proposal is merged by a sensitive owner who is not its author. Never by the proposer, never by momentum.
- Never close someone else's PR without asking first. If it has problems, comment or request changes instead.
- Never force anything: no force-push, no bypassing branch protection.
- If branch protection requires reviews the PR doesn't have, the merge fails; report that plainly instead of reaching for a workaround.
Self-improvement
At the end of the run, check it against these friction triggers: avoidable
round-trip · improvisation · breakage · token waste · operator correction
(full definitions in skills/_improvements/capture.md). If at least one fired,
ask the operator "there was friction on X, should I log it?"; on their ok,
append an entry to skills/_improvements/friction-log.md in the format
capture.md defines. Clean run: say nothing. Never self-edit this skill;
improvements go through /skill-improve.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

