agentsclimarketplace
Sign in

Git pr reviewer

Skill bg-szy/TOP-SKILLS/skills/claude-skills/git-pr-reviewer

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

Install
npx -y skills add bg-szy/TOP-SKILLS --skill git-pr-reviewer

Assembled 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.
  • 5 stars5 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.

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:

  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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.