review-pr
Skill4 starsChanged 3 months agoMITView on GitHub
Perform a comprehensive code review of branch or pull-request changes — bugs, design, security, test coverage. Use when you want a broad review rather than the focused testing/complexity passes.
185 other projects use a version of this.
Adopted by
Most recently taken up by
- torrust/torrust-trackertheir own version, first seen Nov 16, 2026
- Wendor/teapod-streamtheir own version, first seen Nov 16, 2026
- testcontainers/testcontainers-javatheir own version, first seen Nov 16, 2026
- hotcodepush-team/skillstheir own version, first seen Nov 16, 2026
- chuckplayer/claude-agent-packtheir own version, first seen Nov 16, 2026
- ayoubben18/ab-methodtheir own version, first seen Nov 15, 2026
Used with
Projects with it also use diagnose-ci-failures, review-delta 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
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
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
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 versions185 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 185
- 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
175 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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adapter-contract-testingSkill
- azure-devops-prSkill
- bugszero-root-causeSkill
- legacy-3pSkill
- port-refactoringSkill
- quality-gateSkill
- review-ai-writingSkill
- review-allSkill
- review-architectureSkill
- review-complexitySkill
- review-driftSkill
- review-impactSkill
- review-securitySkill
- review-slopSkill
- review-testingSkill
- scope-challengeSkill
- teams-local-messagesSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 178 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 67
Test quality (missing tests, weak assertions)
“Common” is measured: kept by at least 6 in 10 of the 178 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
Code Review Skill
Performs a comprehensive AI-powered code review of changes between refs. For deeper focused
passes, also run review-complexity and
review-testing.
Protocol: docs/review-protocol.md — arguments, ref resolution, exhaustiveness, severity levels, report shape. Read it first.
Its § 4 Be exhaustive is mandatory; the lens steps it refers to are step 2 (Analyze changes) below.
Standards to review against, so a finding cites a rule rather than a preference:
code-design-rules.md (types and exceptions),
hexagonal-architecture-rules.md (where code
goes — only where the codebase is actually hexagonal), testing-rules.md
(what a test must look like), and the project's conventions doc for what it has already
decided on purpose.
Process
- Resolve refs and gather the diff — per
review-protocol.md. - Analyze changes
- Review all modified files for bugs, design issues, and quality problems.
- Evaluate test coverage, identify security concerns, assess architectural decisions.
- Categorize issues by severity (Critical / Major / Minor — see criteria below).
- Confirm § 4 of the protocol is satisfied, then generate report →
reviews/code-review-issues.mdwith file locations, line numbers, clear problem descriptions, concrete fixes, and summary statistics.
Review Criteria
Critical Issues
- Logic errors and incorrect implementations
- Security vulnerabilities
- Breaking changes
- Missing error handling for critical paths
- Race conditions or concurrency bugs
- Resource leaks
Major Issues
- Architecture violations (layering, dependency direction)
- Tight coupling between modules
- Missing abstractions
- Incomplete implementations
- Significant performance concerns
- Poor error-handling patterns
Minor Issues
- Code duplication
- Dead code
- Inconsistent naming or patterns
- Test quality (missing tests, weak assertions)
- Missing documentation for complex logic
- Minor performance optimizations
Exclusions
- Style/formatting (assumed handled by linters)
- Personal preferences without technical merit
- Issues already flagged by automated tools
Output Format
# Code Review Issues: branch-name
## Critical Issues
### 1. Title
**Location:** path/to/file:123
**Issue:** Clear description
**Fix:** Concrete suggestion
## Major Issues
...
## Minor Issues
...
## Summary
- X Critical, Y Major, Z Minor issues
- Overall assessment and recommendationsExample Usage
review-pr # Current branch vs main
review-pr feat/foo # Specific branch
review-pr feat/foo dev # Different base
review-pr 3574 # PR/MR by numberDoes 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.

