code-reviewer

Review local Git changes and GitHub pull requests for code quality.

6|1|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/Ven0m0/claude-config --skill code-reviewer-ven0m0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/Ven0m0/claude-config/tree/main/.gemini/skills/code-reviewer
Command: npx skills add https://github.com/Ven0m0/claude-config --skill code-reviewer-ven0m0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of conducting thorough code reviews, ensuring code quality, maintainability, and adherence to project standards for both local development and remote pull requests.

Core Features & Use Cases

  • Local Code Review: Analyzes staged and unstaged changes in your local repository.
  • Remote PR Review: Checks out and reviews code from remote Pull Requests using the GitHub CLI.
  • Comprehensive Analysis: Evaluates correctness, maintainability, readability, efficiency, security, error handling, and testability.
  • Structured Feedback: Provides clear, constructive feedback with a summary, findings (critical, improvements, nitpicks), and a conclusion.

Quick Start

Review the current local changes in the repository.

Frequently Asked Questions about code-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review for local Git changes and remote GitHub pull requests?

Automating code review for local Git changes and remote GitHub pull requests involves analyzing code for correctness, maintainability, and security. The process evaluates staged, unstaged, and remote PR code to provide structured feedback with critical issues and improvements.

What does a comprehensive code review cover for maintainability and security?

A comprehensive code review evaluates correctness, maintainability, readability, efficiency, security, error handling, and testability. It analyzes code changes to identify critical issues, suggest improvements, note nitpicks, and provide a final structured recommendation.

Do I need Git and GitHub CLI to review remote pull requests?

Yes, Git and GitHub CLI are required to review remote pull requests. Git handles local repository operations and local change analysis, while GitHub CLI is specifically required for checking out and reviewing code from remote pull requests.

How do I check out and review a remote GitHub pull request locally?

Checking out and reviewing a remote GitHub pull request locally requires using GitHub CLI to fetch the PR code into your local environment. The code is then analyzed for correctness, security, and testability to generate structured feedback and a final conclusion.

What is the best way to structure pull request feedback for refactoring and debugging?

Structuring pull request feedback for refactoring and debugging involves categorizing findings into critical issues, improvements, and nitpicks. This structured approach ensures clear, constructive feedback culminating in a final recommendation.

Can I analyze unstaged changes in my local repository for code quality?

Yes, unstaged changes in your local repository can be analyzed for code quality. Local code review functionality evaluates both staged and unstaged changes to assess readability, efficiency, and security before committing.