Skip to main content
subagent CX Codex

code-reviewer · zebbern — Claude Code subagent for reviewing changes

code-reviewer is a Claude Code subagent that checks completed work for bugs and regressions. It runs after implementation or when an existing diff needs review.

MIT ★ 4,719 updated 2026-10-30

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

What code-reviewer does

code-reviewer inspects a diff and its surrounding code for concrete bugs, regressions, compatibility problems, concurrency issues, and gaps in verification. It reads project instructions and the baseline, then follows changed behavior through callers and error paths.

The subagent leaves files untouched and excludes speculative findings. It ranks actionable issues by severity, with a path:line location, a triggering scenario, the impact, and a direction for remediation. If the intended behavior or comparison baseline is unavailable, it returns blocked; if missing or generated source prevents tracing an important path, it returns inconclusive. For Claude Code, place the agent file at .claude/agents/code-reviewer.md.

What it helps with

  • find a concrete bug in a diff
  • catch regressions in changed behavior
  • check compatibility across callers
  • spot verification gaps around modified code

Example prompts for the agent

  • Review the current diff and report only actionable problems.
  • Check this patch for regressions and compatibility issues without editing files.
  • Trace the changed behavior through its callers and describe any failure scenario.

How to install code-reviewer

Manually: put the files in place

.claude/agents/code-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 code-reviewer

How do I install code-reviewer in Claude Code?

Add the agent file at .claude/agents/code-reviewer.md.

What does code-reviewer do?

It reviews existing changes for actionable bugs, regressions, concurrency issues, and compatibility problems. It does not edit the implementation.

When does code-reviewer return blocked or inconclusive?

It returns blocked when the intended behavior or comparison baseline is unavailable. It returns inconclusive when missing or generated source prevents tracing a potentially important changed path.

Source text

code-reviewer.md · MIT
---
name: code-reviewer
description: "Use proactively after an implementation or when an existing diff needs correctness, regression, concurrency, compatibility, and meaningful verification review. Do not use for implementation or a dedicated exploitability assessment."
tools:
  - Read
  - Grep
  - Glob
  - Bash
  - PowerShell
  - LSP
model: opus
permissionMode: plan
effort: max
---

# Mission

Review an existing change for actionable correctness and regression risks. Own diff review; do not edit the implementation.

## Method

1. Read the requested outcome, repository instructions, baseline, diff, and relevant surrounding code.
2. Trace changed behavior into callers, consumers, state transitions, errors, and compatibility boundaries.
3. Check for concrete correctness, regression, concurrency, cleanup, and verification failures.
4. Search for missed sibling occurrences only when the change claims a systemic fix.
5. Rank only findings that would justify changing the patch.

## Constraints

- Do not edit files, implement fixes, or manufacture findings.
- Exclude style preferences, generic hardening, and speculative risks without a reachable failure scenario.
- Treat a green suite as insufficient when it does not exercise the changed boundary.
- If no actionable findings exist, say so explicitly and state what was inspected.

## Output

Begin with:

ROLE: code-reviewer
STATUS: complete|blocked|inconclusive

Then list findings in severity order. Each finding must include `[P0]` through `[P3]`, a precise `path:line` location, the triggering scenario, concrete impact, and remediation direction. Follow with scope inspected, verification gaps, and an evidence-backed no-findings statement when applicable.

## Stop conditions

Return `blocked` when the intended behavior or comparison baseline is unavailable. Return `inconclusive` when generated, vendored, or missing source prevents tracing a potentially important changed path.

© zebbern · MIT · zebbern/claude-code-guide

Similar subagents

All subagents for Code review and refactoring →

code-reviewer by other authors comes first.

code-reviewer official Anthropic code-reviewer reviews code changes against CLAUDE.md project rules and flags material defects. Run it before a commit or pull request. CX Codex 31,050installs code-reviewer official Anthropic The code-reviewer subagent checks code changes for bugs, security issues, and project-rule violations. Use it when a review should focus on findings that matter. CX Codex 31,050installs code-reviewer VoltAgent Community code-reviewer reviews code changes for bugs, security flaws and maintenance issues. Use it before merging complex work or auditing a project. CX Codex 31,050installs code-reviewer ChrisWiles code-reviewer — a subagent for Claude Code that checks newly written or modified code against project standards, TypeScript strict mode, and security patterns. CX Codex ★ 6,091repo stars code-reviewer Affaan Mustafa The code-reviewer subagent reviews code changes for security vulnerabilities, bugs, performance problems, and style violations. Run it immediately after writing or modifying code to catch issues before they reach production. CX Codex ★ 6,739repo stars cleanup-reviewer alfredoperez cleanup-reviewer reviews a specified slice of a repository cleanup diff and reports findings only. Use it when the review should stay within named files. CX Codex ★ 110repo stars code-review waybarrios code-review reviews pull requests and local diffs for bugs and convention violations using multi-agent checks. Helps uncover subtle logic flaws before merging changes. CX Codex +1 477installs culprit noordeen123 culprit searches Git history for likely causes of a bug and checks whether a proposed fix leaves callers untouched. Use it to review a patch before committing. CX Codex +1 ★ 6repo stars dev-team-reviewer Jerome Hardaway, Vets Who Code The dev-team-reviewer subagent for Claude Code assesses a portfolio and GitHub repositories from a hiring engineer’s perspective. It checks code, engineering choices, tests, and whether the evidence fits the claimed level. CX Codex ★ 73repo stars check tw93 Inspects diffs, evaluates PRs, and verifies release readiness. It runs report-only checks and will not alter files without explicit user consent. CX Codex +1 16,500installs deslop cursor deslop inspects branch diffs against main to remove AI-generated code clutter and inconsistent styling. Ideal for polishing branch changes before pull request review. CX Codex +1 10,700installs

From the same set86

The whole set →
setup-use-import-maps setup-use-import-maps — a rule that swaps the old Three.js CDN <script src> tag for an import map with ES modules and a pinned version. CX Codex +1 ★ 4,719repo stars render-delta-time render-delta-time instructs agents to use delta time in animation loops so motion remains consistent across all display refresh rates. CX Codex +1 ★ 4,719repo stars memory-dispose-geometry memory-dispose-geometry is a Claude Code rule that tells the agent to release geometry when removing scene objects. It applies to Three.js resource cleanup. CX Codex +1 ★ 4,719repo stars root-cause-debugger The root-cause-debugger subagent for Claude Code and Codex reproduces failures and finds bug root causes before code changes. It helps diagnose bugs without editing code. CX Codex ★ 4,719repo stars perf-visibility-toggle perf-visibility-toggle guides the AI to toggle the visible prop on Three.js components rather than conditionally unmounting them, avoiding GPU shader recompilation. CX Codex +1 ★ 4,719repo stars perf-r3f-perf The perf-r3f-perf rule teaches Claude Code about r3f-perf, a performance monitoring library for Three.js scenes in real time. Spot frame drops, memory leaks, and unnecessary matrix recalculations as they happen. CX Codex +1 ★ 4,719repo stars codebase-mapper codebase-mapper maps repository structure, call chains, and data flows before code changes without mutating any files. CX Codex ★ 4,719repo stars solution-architect solution-architect is a subagent for Claude Code, Codex, and Cursor that compares architectural options and recommends one based on constraints. It is used when requirements are set but several designs are viable. CX Codex ★ 4,719repo stars

Project sponsors

Companies that keep this analytics open