
Git Pr Reviewer
- 248 installs
- 237 repo stars
- Updated July 15, 2026
- onewave-ai/claude-skills
Review pull requests for bugs, style, security risks, missing tests, and merge readiness before code lands on main.
About
Git-pr-reviewer analyzes pull request diffs and descriptions to surface logic bugs, missing tests, breaking API changes, and style issues, delivering actionable review comments aligned with team merge standards.
- Diff-aware feedback
- Test coverage gaps
- Security smell checks
- Style consistency
- Merge readiness verdict
Git Pr Reviewer by the numbers
- 248 all-time installs (skills.sh)
- +5 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #158 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/onewave-ai/claude-skills --skill git-pr-reviewerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 248 |
|---|---|
| repo stars | ★ 237 |
| Last updated | July 15, 2026 |
| Repository | onewave-ai/claude-skills ↗ |
What it does
Review pull requests for bugs, style, security risks, missing tests, and merge readiness before code lands on main.
Files
Git PR Reviewer
Instructions
When reviewing a pull request:
1. Get the diff: Run git diff main...HEAD or git diff <base-branch>...HEAD 2. Analyze changed files: Identify all modified, added, and deleted files 3. 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