Review PR

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.

116 stars 32 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add SeifBenayed/cloclo --skill review-pr
Manual install
git clone --depth 1 https://github.com/SeifBenayed/cloclo.git /tmp/cloclo
mkdir -p ~/.claude/skills
cp -r /tmp/cloclo/.claude/skills/review-pr ~/.claude/skills/review-pr

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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
Read the full skill on GitHub

Details

Skill name
review-pr
Path
.claude/skills/review-pr/SKILL.md
License
MIT
Repo updated
5 April 2026

FAQ

What does the Review PR skill do?

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.

How do I install the Review PR skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add SeifBenayed/cloclo --skill review-pr. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Review PR popular?

It lives in SeifBenayed/cloclo, which has 116 GitHub stars and 32 forks, and is included in 1 curated skill list.

Related skills

XLSX

116

SeifBenayed/cloclo

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or rest

Documents & Office FilesIn 1 list32

PPTX

116

SeifBenayed/cloclo

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the con

Documents & Office FilesIn 1 list32

DOCX

116

SeifBenayed/cloclo

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'lette

Documents & Office FilesIn 1 list32

Code Review

192

smallnest/goskills

专业的代码审查助手,提供结构化的审查流程、详细的检查清单和建设性的反馈指南。适用于审查Pull Request、代码提交或任何需要代码质量评估的场景,涵盖功能性、安全性、性能、测试、文档、架构设计等多个维度。

Git & Code Review27

Commit

116

SeifBenayed/cloclo

Create a git commit with a good message. Use when the user says "commit", "save changes", "commit this", or asks to create a commit after making code changes.

Git & Code ReviewIn 1 list32

Git Workflow Expert

272

curiositech/some_claude_skills

Git branching strategies, conflict resolution, rebase workflows, monorepo patterns, and advanced operations like cherry-pick, bisect, and reflog recovery. Activate on "git", "branching strategy", "merge conflict", "rebase", "cherry-pick", "monorepo git", "git bisect", "git reflog", "squash commits". NOT for GitHub Actions CI/CD (use github-actions-pipeline-builder), GitHub API/webhooks, or PR review processes (use code-review-checklist).

Git & Code Review46

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.