code-reviewer

Review local git diffs and remote Pull Requests with prioritized feedback.

965|142|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/vigolium/vigolium --skill code-reviewer-vigolium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/vigolium/vigolium/tree/main/platform/vigolium-audit/src/content/skills/code-reviewer
Command: npx skills add https://github.com/vigolium/vigolium --skill code-reviewer-vigolium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps developers and teams catch correctness, maintainability, readability, efficiency, and security issues before they land in a codebase, whether the changes are local or proposed via a Pull Request.

Core Features & Use Cases

  • Remote PR reviews: Review code by PR number or URL using GitHub checkout, then validate context with existing PR description and comments.
  • Local change reviews: Review staged and unstaged changes by inspecting git status and diffs when no PR is specified.
  • Actionable feedback: Produce a structured review with categorized findings (critical, improvements, optional nitpicks) and a clear recommendation (Approved / Request Changes).

Quick Start

Ask the AI to review your current changes, or tell it which Pull Request to review, and include what you want the reviewer to focus on (e.g., security, tests, or maintainability).

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review local git changes for maintainability and security before committing?

To review local git changes, the Skill inspects staged and unstaged diffs to evaluate maintainability, security, and testability, returning prioritized feedback with an approval or request-changes recommendation.

Can I review a GitHub Pull Request by its URL or PR number?

You can review a GitHub Pull Request by URL or number using GitHub CLI checkout, validating context with existing PR descriptions and comments to provide structured feedback.

What categories of feedback does a structured code review cover?

A structured code review provides categorized findings including critical issues, improvements, and optional nitpicks, focusing on correctness checks, maintainability, readability, security scrutiny, and testability guidance.

Do I need to specify what the code review should focus on?

Specifying focus areas like security, tests, or maintainability is recommended to tailor the review, but the Skill automatically evaluates correctness, efficiency, and readability by analyzing git diffs and PR context.

Does the code review require a specific environment to run?

The code review requires a git-based environment for local mode change detection, or GitHub CLI checkout plus preflight and context gathering for PR mode to analyze diffs and return feedback.