Git Pr Reviewer Skill for Claude

Review pull requests for code quality, security issues, and best practices. Use when reviewing PRs, checking code changes, or analyzing diffs before merge.

464 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

235

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/OneWave-AI/claude-skills --skill git-pr-reviewer

The instruction itself

9 sections, as written by the author

Git PR Reviewer

Instructions

When reviewing a pull request:

Get the diff: Run git diff main...HEAD or git diff <base-branch>...HEAD
Analyze changed files: Identify all modified, added, and deleted files
Review each file for:
Logic errors and bugs
Security vulnerabilities (SQL injection, XSS, hardcoded secrets)
Performance issues (N+1 queries, unnecessary re-renders, memory leaks)
Code style and consistency
Missing error handling
Test coverage gaps

Review Checklist

Security

[ ] No hardcoded credentials or API keys
[ ] Input validation on user data
[ ] Proper authentication/authorization checks
[ ] No SQL injection vulnerabilities
[ ] XSS prevention in place

Code Quality

[ ] Functions are small and focused
[ ] No code duplication
[ ] Clear variable/function naming
[ ] Proper error handling
[ ] No unused imports or dead code

Performance

[ ] No unnecessary database queries
[ ] Efficient algorithms used
[ ] Proper caching where needed
[ ] No memory leaks

Testing

[ ] New code has tests
[ ] Edge cases covered
[ ] Tests are meaningful, not just for coverage

Output Format

## PR Review Summary

### Overview
[Brief summary of changes]

### Issues Found
#### Critical
- [Issue description + file:line]

#### Warnings
- [Issue description + file:line]

#### Suggestions
- [Improvement ideas]

### Approval Status
[APPROVE / REQUEST CHANGES / NEEDS DISCUSSION]

Example

# Review current branch against main
git diff main...HEAD --stat
git diff main...HEAD

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take onewave-ai/git-pr-reviewer from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.