Skip to main content
subagent CX Codex

reviewer · mralexivy — Claude Code subagent: what it does, how to install

The reviewer subagent for Claude Code performs an independent audit of code changes. It evaluates completed work against original task requirements and acceptance criteria, identifying critical issues.

MIT ★ 80 updated 2026-11-17

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/reviewer.md
Open on GitHub

What reviewer does

The agent operates in read-only mode to analyze git diff for quality control. It inspects security compliance, API compatibility, and potential performance risks in modified files.

Running the agent requires the opus model. It classifies findings as defect or evidence_gap while providing specific fix instructions for blockers. The final output includes a verdict of approve, approve_with_notes, or changes_required.

What it helps with

  • Verify code against acceptance criteria
  • Identify critical vulnerabilities before merging
  • Audit implementation without relying on the author
  • Detect architecture defects

Example prompts for the agent

  • Run a review for the current PR
  • Check changes in src/auth.ts against the task

How to install reviewer

Manually: put the files in place

.claude/agents/reviewer.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about reviewer

How to install reviewer in Claude Code?

Copy the configuration file to .claude/agents/reviewer.md.

What does reviewer do?

It performs an independent code analysis after a task is finished to ensure it meets all specified requirements and identifies potential risks.

What is required to run reviewer?

Use the opus model, ensure access to git, grep, bash commands, and place the configuration file in the agent folder.

Source text

reviewer.md · MIT
---
name: reviewer
description: AutoMode independent reviewer (Opus). Evidence-first, read-only review of a finished change against the original task, acceptance criteria, and raw verification checks. Runs by review policy and mandatory risk rules.
tools: Read, Grep, Glob, Bash
model: opus
maxTurns: 30
color: red
---

You are the AutoMode independent reviewer. You get the original task, the acceptance criteria, the forbidden changes, the raw verification checks, and the changed-file list. You do not get the implementers' own account. You read the diff and the code yourself, and you judge from that evidence.

When the main session calls you directly, the prompt has the request, the acceptance criteria, the check commands with their output, and the changed files. Return your verdict (`approve`, `approve_with_notes`, or `changes_required`), then each finding with its severity (blocker, major, or minor), its kind, `path:line`, the problem, and the fix. Keep it short. The main session fixes the blocker defects.

Rules:
- Read only. Use Bash only for `git diff`, `git diff --stat`, and `git status`. Limit `git diff` to the changed files the prompt lists.
- Check these areas: correctness against the task and each acceptance criterion, forbidden changes, architecture, security, API compatibility, concurrency, tests that were weakened or are missing, and significant performance risk.
- Treat a failed or unverified verification as unproven work. Do not approve a change whose checks fail unless the failure is clearly unrelated and you say why.
- Read surrounding code when the diff alone does not show whether a change is safe.
- Do not report style issues or small improvements. Report only problems that a senior engineer would block or flag before a merge.
- For each finding, give the file, the problem, and the specific fix.
- Set each finding's kind. Use `defect` when you read the code and it is wrong. Use `evidence_gap` when you could not establish a fact, and say which fact and how to check it. A gap is never a defect: the workflow sends a defect to an implementer and a gap to the verifier.
- Use `changes_required` only when at least one finding is a blocker defect.

© mralexivy · MIT · mralexivy/AutoMode

Similar subagents

All subagents for Code review and refactoring →

reviewer by other authors comes first.

reviewer VoltAgent reviewer is a Codex subagent for PR-style checks of correctness, security, regressions, and test gaps. It joins tasks that call for a focused code review. CX Codex ★ 6,505repo stars reviewer Rohit Ghumare reviewer — a subagent that reviews code line by line, reading actual files and citing every finding with exact quotes. Use before committing, during PR review, or after major changes. CX Codex ★ 2,966repo stars reviewer ruvnet A reviewer persona for Claude that reads a change like a senior engineer: behaviour, security holes, slow paths, standards, docs. You get a summary with critical issues. CX Codex ★ 850repo stars gem-reviewer official github gem-reviewer is a GitHub Copilot subagent that performs independent reviews of plans, code, and configurations. It identifies risks and potential issues in development workflows. CX Codex +1 ★ 41,430repo stars skill-quality-reviewer Galaxy-Dawn skill-quality-reviewer audits local skills across description quality, structure, and writing style. Generates weighted letter grades and prioritized remediation plans before sharing. CX Codex +1 467installs adversarial-reviewer ekreloff The adversarial-reviewer skill reviews changes through Saboteur, New Hire, and Security Auditor personas. Use it before merging a PR or when Claude is too agreeable. CX Codex +1 813installs code-reviewer zhaono1 code-reviewer reviews Git diffs and pull requests for security vulnerabilities, logic flaws, test coverage, and code quality. CX Codex +1 760installs karpathy-coder claude-code-skills karpathy-coder is a Claude Code skill that checks code against four Karpathy principles: surface assumptions, keep changes simple, limit edits to the task, and define verifiable goals. CX Codex +1 1,053installs ns-reviewer nextstage-brasil ns-reviewer grades code changes against SOLID principles, clean code patterns, performance, security, and testability. Approves only at score 10; score 9 triggers rejection. CX Codex +1 140installs

From the same set10

The whole set →
explorer The explorer subagent for Claude Code gathers repository facts for a planner. It identifies dependencies, build commands, and tests before task planning begins. CX Codex ★ 80repo stars implementer implementer is a Claude Code subagent that carries out one workstream from an approved plan. It edits its assigned files, adds tests, and runs validation. CX Codex ★ 80repo stars builder builder is a Claude Code subagent that takes a standalone task brief, edits the working tree, and loops through project checks until they pass. Runs for rescue attempts and dedicated build tasks. CX Codex ★ 80repo stars verifier verifier is a Claude Code subagent that runs tests, type checks, and builds after code changes. It reviews the diff for regressions and repairs defects caused by the current work. CX Codex ★ 80repo stars architect architect is a Claude Code subagent that turns discovery summaries into an architecture plan. It assigns file ownership and defines acceptance checks. CX Codex ★ 80repo stars growth growth is a Claude Code skill for AutoMode’s weekly promotion cycle. Ask it to draft social posts, check catalogue submissions, find listings, or report traffic and stars. CX Codex +1 ★ 80repo stars publish-results publish-results is a Claude Code skill that propagates benchmark figures across project docs and site files. Runs before merging release PRs or after altering public metrics. CX Codex +1 ★ 80repo stars ship-change ship-change is a Claude Code skill that guides repository changes from issue to merged PR. It activates before fixes, features, docs edits, refactors, and release requests. CX Codex +1 ★ 80repo stars

Project sponsors

Companies that keep this analytics open