review-pr · seifbenayed — Claude Code skill: pull request review
Walks a branch diff against a checklist: bugs, security, performance, tests. Ends with a verdict — approve, request changes or discuss.
npx skills add SeifBenayed/cloclo --skill review-pr -a claude-codeWhat review-pr does
The skill diffs your current branch against the base one and goes through the changes file by file. It tries main first, then master, and asks if neither exists. Commits come from git log --oneline <base>..HEAD, the whole diff from git diff <base>...HEAD. When the diff is large it drops to a single file: git diff <base>...HEAD -- <file>.
Every changed file gets checked for logic errors, null or undefined access, race conditions, injection, XSS, auth bypass, hardcoded secrets, SSRF, N+1 queries, unbounded loops, memory leaks and swallowed exceptions. Style drift and missing tests for new behaviour or edge cases are flagged too.
The output is a short summary, a list of problems worth fixing before merge, non-blocking suggestions and a verdict. File paths and line numbers are expected, and fixes should be concrete. The skill only holds Bash, Read, Grep and Glob, so it never edits your code — you apply the fixes yourself.
What it helps with
- scan a branch diff for bugs before merging
- spot a hardcoded secret or auth bypass in the changes
- catch N+1 queries and memory leaks in new code
- check that new functionality comes with tests
- get a structured verdict on a pull request
Example prompts for the agent
- Review the current branch against main
- Check this pull request for bugs and security issues
- Look at the diff for
src/api/users.tsand tell me what to fix before merge
How to install review-pr
1Skills CLI (Vercel)
npx skills add SeifBenayed/cloclo --skill review-pr -a claude-code2Manually: put the files in place
~/.claude/skills/review-pr/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/review-pr/
1Skills CLI (Vercel)
npx skills add SeifBenayed/cloclo --skill review-pr -a codex2Manually: put the files in place
.agents/skills/review-pr/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add SeifBenayed/cloclo --skill review-pr -a cursor2Manually: put the files in place
.cursor/skills/review-pr/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install SeifBenayed/cloclo review-pr2Manually: put the files in place
.github/skills/review-pr/SKILL.md1Skills CLI (Vercel)
npx skills add SeifBenayed/cloclo --skill review-pr -a gemini-cli2Platform CLI
gemini skills install https://github.com/SeifBenayed/cloclo --path .claude/skills/review-prManually: put the files in place
.devin/skills/review-pr/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add SeifBenayed/cloclo --skill review-pr -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about review-pr
How do I install review-pr in Claude Code?
Run npx skills add SeifBenayed/cloclo --skill review-pr -a claude-code. The skill lands in ~/.claude/skills/review-pr/SKILL.md.
What does review-pr do?
It compares your branch with the base branch and checks the changes for bugs, vulnerabilities, performance problems, error handling gaps and missing tests. Then it gives a verdict: approve, request changes or needs discussion.
Which tools can the skill use?
Bash, Read, Grep and Glob. It reads and searches files but does not modify code.
Source text
SKILL.md · MIT
--- name: review-pr description: Review a pull request for bugs, security issues, and improvements. Use when the user asks to review a PR, review changes, or check code quality of a branch. allowed-tools: Bash, Read, Grep, Glob --- # Pull Request Review Review the current branch's changes compared to the base branch. ## Steps 1. Determine the base branch: - Try `main`, then `master`, then ask - Run `git log --oneline <base>..HEAD` to see all commits in this PR 2. Run `git diff <base>...HEAD` to see the full diff 3. For large diffs, review file-by-file using `git diff <base>...HEAD -- <file>` 4. For each changed file, check for: - **Bugs**: logic errors, off-by-one, null/undefined access, race conditions - **Security**: injection, XSS, auth bypass, hardcoded secrets, SSRF - **Performance**: N+1 queries, unbounded loops, missing indexes, memory leaks - **Error handling**: missing try/catch, swallowed errors, unclear error messages - **Style**: inconsistency with the rest of the codebase - **Tests**: missing tests for new functionality or edge cases 5. Provide a structured review: **Summary** — What the PR does (1-2 sentences) **Issues** — Bugs, security, or correctness problems that should be fixed before merge **Suggestions** — Non-blocking improvements worth considering **Verdict** — Approve / Request Changes / Needs Discussion Be specific — reference file paths and line numbers. Suggest concrete fixes, not vague advice. $ARGUMENTS
© SeifBenayed · MIT · SeifBenayed/cloclo
Similar skills
All skills for Code review and refactoring →review-pr by other authors comes first.