code-reviewer

Reviews local git changes or remote GitHub Pull Requests for correctness, maintainability, and security.

2|2|Updated Jun 28, 2015
One-click install
npx skills add https://github.com/camercu/dotfiles --skill code-reviewer-camercu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/camercu/dotfiles/tree/main/common/.config/agents/skills/code-reviewer
Command: npx skills add https://github.com/camercu/dotfiles --skill code-reviewer-camercu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Conducting thorough, consistent code reviews is time-consuming and easy to do superficially, especially when switching between local changes and remote Pull Requests. This Skill provides a structured review workflow that catches bugs, security issues, and maintainability problems before they reach production. ## Core Features & Use Cases - Dual Review Targets: Reviews either local changes (staged or working tree diffs) or remote GitHub Pull Requests by ID or URL, checking out PRs with the GitHub CLI. - Structured Analysis Pillars: Evaluates code across correctness, maintainability, readability, efficiency, security, edge cases, and testability. - Incremental Findings Recording: Writes each finding to a file as it is discovered, so results survive session limits or crashes, and classifies them as Critical, Improvements, or Nitpicks with a clear approval recommendation. - Use Case: A teammate asks you to review PR #123. The Skill checks out the PR with gh pr checkout, runs the project's just ci preflight suite, analyzes the diff, and produces a structured review with file:line evidence and an Approved or Request Changes conclusion. ## Quick Start Ask the agent to review PR #123 or to review your current uncommitted changes.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review a GitHub Pull Request with an AI agent?▼

Provide the PR number or URL and ask for a review. The Skill checks out the PR using gh pr checkout, runs the project's verification suite such as just ci, reads the PR description and comments, then analyzes the diff and returns structured findings.

How to review local uncommitted git changes before pushing?▼

Ask to review your changes without mentioning a PR. The Skill inspects git status, git diff for the working tree, and git diff --staged for staged changes, then analyzes them across correctness, security, and maintainability pillars.

What does the code review check for?▼

The review covers seven pillars: correctness, maintainability, readability, efficiency, security, edge cases and error handling, and testability. Findings are classified as Critical, Improvements, or Nitpicks, ending with an Approved or Request Changes recommendation.

Can the same agent review code it wrote itself?▼

The Skill warns against self-review when no independent party will vet the findings, since a context is primed to see its own work as correct. In autonomous agent chains it recommends spawning a fresh agent to run the review.

Why record review findings to a file during analysis?▼

Findings are appended to a file as they are discovered rather than batched at the end, because context can be lost to session limits, compaction, or crashes. For long reviews or delegated agents, the findings file itself is the deliverable.