review-pr
Skill3 starsChanged 6 months agoApache-2.0View on GitHub
Review a GitHub pull request (\"review PR 123\", a PR URL) or a named branch or ref and write a review report, the review-loop review-pr; also when the user explicitly asks for review-pr. A general request to review local changes (\"review my changes\") is not this skill (review-loop). It runs the paired-session report mode (no writer, nothing committed or posted). Not for implementing a work item (review-loop).
186 other projects use a version of this.
Adopted by
Most recently taken up by
- ayoubben18/ab-methodtheir own version, first seen Nov 15, 2026
- jameswyse/skillstheir own version, first seen Nov 15, 2026
- connext-solutions/flowctltheir own version, first seen Nov 15, 2026
- atomicinnovation/acceleratortheir own version, first seen Nov 14, 2026
- suitedaces/dorabottheir own version, first seen Nov 14, 2026
- AMD-AGI/Hyperloomtheir own version, first seen Nov 12, 2026
Used with
Projects with it also use diagnose-ci-failures, docs-loop 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.
zerx-labSkilldiagnose-ci-failures
Diagnose CI failures for a PR using the GitHub CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate PR build failures.
Also in 3 projects that use this
GeiserXSkilldocs-loop
Use when the user asks to audit docs, check documentation for stale claims, or verify docs against the code.
Also in 3 projects that use this
GeiserXSkillfull-loop
Drive a repository to done with sergio-loop, then keep improving it with refine-loop at a descending theta. Use only when the user explicitly invokes full-loop.
Also in 3 projects that use this
n24q02mSkillreview-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
Also in 3 projects that use this
n24q02mSkillbuild-graph
Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.
Also in 3 projects that use this
- +7 more from GeiserX
Other versions186 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 186
- denoland/deno★ 109ksame name
- ToolJet/ToolJet★ 41ksame name
- remix-run/remix★ 33ksame name
- tirth8205/code-review-graph★ 33ksame name
- alpinejs/alpine★ 32ksame name
- nrwl/nx★ 29ksame name
- PrefectHQ/fastmcp★ 29ksame name
- jlowin/fastmcp★ 29ksame name
- livewire/livewire★ 24ksame name
- microsoft/fluentui★ 20ksame name
176 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 repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- guideSkill
- paired-sessionSkill
- review-loopSkill
- code-quality-loopSkill
- guideSkill
- paired-sessionSkill
- reorganizeSkill
- review-loopSkill
- review-prSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 179 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
If the paired-session skill reports stage A failure: <reason>, report review-pr: paired-session entry refused (<reason>) and stop (nothing …
“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
review-pr (Codex)
A repository with submodules cannot be reviewed in report mode yet.
Resolve entry in .review-loop/config.md (exact values legacy and paired-session): legacy is
refused with review-pr: the legacy workflow was removed in v2.13.0; remove "entry: legacy" from .review-loop/config.md (paired-session is the only entry); an invalid value prints
review-pr: entry "<v>" is not valid (paired-session is the only entry); using paired-session, a duplicate key or an
unreadable config prints review-pr: entry could not be read (<reason>); using paired-session, and both continue as
absent. <support-root> is this plugin, not the task workspace.
- The user asks for "the legacy review-pr workflow": refused with
review-pr: the legacy workflow was removed in v2.13.0; ask for a review-pr without the legacy workflow (report mode). - A host that is neither macOS (
uname -sisDarwin) nor native Windows (PowerShell:$env:OS -eq 'Windows_NT'; Git Bash:uname -sstarts withMINGW64_NT-orMSYS_NT-): refused withreview-pr: paired-session needs macOS or native Windows; Linux (WSL included) and other hosts are not supported. - Otherwise the paired route. Print
review-pr: paired-session report mode (entry set in .review-loop/config.md)when the key is set, orreview-pr: paired-session report mode (the default entry)when it is absent. Hand the request (input and aspects) to the Codexpaired-sessionskill as a review-pr handoff and end this skill. It loads the shared contract and follows its Review-PR entry: a PR or ref is reviewed in a temporary clone, no tests run unless the user confirms a test command, the result isreview-report.md, and nothing is posted unless the user asks.simplifyis refused there before any coordinator command, with the pointerrun /review-loop:code-quality-loop on the change (its POLISH-Q simplifier)(Claude Code).- If the paired-session skill reports
stage A failure: <reason>, reportreview-pr: paired-session entry refused (<reason>)and stop (nothing falls back).
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.

