Git pr reviewer
Skill bg-szy/TOP-SKILLS/skills/claude-skills/git-pr-reviewer
全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard
npx -y skills add bg-szy/TOP-SKILLS --skill git-pr-reviewerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Review pull requests for code quality, security issues, and best practices. Use when reviewing PRs, checking code changes, or analyzing diffs before merge.
SKILL.md
1.8 KB, 396 tokens by cl100k_base, as published. Nobody here has run it
Git PR Reviewer
Instructions
When reviewing a pull request:
- Get the diff: Run
git diff main...HEADorgit 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
Gives 0 of the 12 instructions most pr commit review skills give in 396 tokens
Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06
- use conventional commits formatin 123 of 888, across 110 files
- keep subject line under 72 charactersin 60 of 888, across 46 files
- delete branches after mergein 50 of 888, across 37 files
- use imperative mood in subject linein 50 of 888, across 41 files
- use imperative mood in commit messagesin 45 of 888
- generate a conventional commit messagein 42 of 888
- make atomic commitsin 37 of 888, across 25 files
- run tests before committingin 36 of 888, across 24 files
- run project test suite to verify clean baselinein 35 of 888, across 7 files
- run detected project setup commandsin 34 of 888, across 6 files
- wrap commit body at 72 charactersin 32 of 888, across 25 files
- split unrelated changes into separate commitsin 32 of 888, across 27 files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.