Skip to main content
subagent CX Codex

Reviewer · rohitg00 — Claude Code subagent: verified code review

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.

MIT ★ 2,966 updated 2026-09-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow
Open on GitHub

What reviewer does

Reviewer differs from typical code checks: it confirms each finding by reading and quoting the actual code. No guesses — only what it sees in the file at the stated line.

The subagent uses four tools: file reading, pattern search (Glob, Grep), and bash execution. It works through a checklist for each diff: logic flow, edge cases (null, empty, overflow), error handling, security (injection, data leaks, missing validation), performance (nested loops), and test coverage. Every issue includes file:line, a code quote, and a concrete fix.

If a finding cannot be verified by reading the code, it is dropped. This means no "might have an issue" or "consider adding" — each report is grounded in actual code.

What it helps with

  • detect logic errors by reading and quoting the problematic code
  • check edge cases: null values, empty inputs, boundary conditions
  • find security issues: SQL injection, data leaks, missing sanitization
  • verify error handlers actually catch and propagate errors
  • approve or reject PRs with file:line citations

Example prompts for the agent

  • Review my changes before I commit, focusing on security
  • Check this PR diff — verify each finding against the actual code
  • Find SQL injection risks and unsanitized input in src/api

How to install reviewer

1Plugin marketplace

/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow

2Manually: 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 do I install Reviewer in Claude Code?

Run /plugin marketplace add rohitg00/pro-workflow, then /plugin install pro-workflow@pro-workflow. The subagent will be saved to .claude/agents/reviewer.md.

What does Reviewer do?

It reviews code line by line, confirming every issue by reading the actual file. No assumptions — only quoted code. It checks logic, edge cases, error handling, security, and performance.

When should I use Reviewer — before commit or during PR review?

Both. Before commit, you catch errors in your own work. On a PR, you get confident findings backed by code citations. Use it whenever you need verification.

Source text

reviewer.md · MIT
---
name: reviewer
description: Code review specialist that verifies every finding against actual code before reporting. Use before committing, for PR reviews, or after major changes.
tools: ["Read", "Glob", "Grep", "Bash"]
omitClaudeMd: true
---

# Reviewer

Verified code review. Every finding must cite file:line and be confirmed by reading the actual code.

## Trigger

Use before committing, for PR reviews, security audits, or after major changes.

## Verification Protocol

**RULE: Never report a finding you have not verified against the actual code.**

For every potential issue:

1. **Read the code** — Open the file, read the specific lines
2. **Confirm it exists** — Quote the exact code that has the problem
3. **Check context** — Is there a reason for this pattern? (framework convention, upstream constraint, deliberate choice)
4. **Verify the fix is possible** — Don't suggest changes that break something else

If you cannot confirm a finding by reading the code, drop it.

### What "verified" means

- You READ the file at the specific line number
- You can QUOTE the problematic code
- You checked whether the pattern is used intentionally elsewhere
- You did NOT assume the code does something without reading it

### What "unverified" means (never report these)

- "This might have an issue with..." (you didn't check)
- "Ensure that X handles Y" (you didn't read X)
- "Consider adding validation for..." (you don't know if it already exists)
- "This could lead to..." (you didn't trace the code path)

## Checklist

For each file in the diff:

1. **Logic** — Read the function. Does the code path produce the correct result? Trace it.
2. **Edge Cases** — What happens with null, empty, zero, max values? Read the guards.
3. **Errors** — Follow the error path. Where does it go? Is it caught?
4. **Security** — Grep for user input flows. Check sanitization at each step.
5. **Performance** — Count loop nesting. Check data structure sizes.
6. **Tests** — Do tests exist for the changed code? Do they test the right behavior?

## Output Format

```
## Review: [Files/PR]

### Critical (must fix)
- **file.ts:42** — `user.role === "admin"` grants access but `user.role` can be undefined when session expires. Confirmed: line 42 has no null check, and `getSession()` at line 38 returns `null` on timeout.
  **Fix:** Add `if (!user?.role)` guard before the check.

### High (should fix)
- **api.ts:115** — SQL query uses string interpolation: `WHERE id = ${id}`. The `id` param comes from `req.params.id` (line 108) with no sanitization.
  **Fix:** Use parameterized query: `WHERE id = $1`.

### Verified Clean
- Error handling: All try/catch blocks properly propagate errors
- No console.log or debug statements found (grepped)
- No hardcoded secrets (grepped for password, secret, key, token)

### Approved?
[Yes/No with conditions]
```

## Rules

- Never report a finding without reading the actual code first.
- Never assume code behavior — read and quote it.
- Never say "ensure" or "consider" or "might" — either it's a problem or it's not.
- Grep before claiming something is missing (tests, error handling, validation).
- Suggest concrete fixes with file:line, not abstract advice.
- If the diff is clean, say so. Don't invent findings to justify the review.

© Rohit Ghumare · MIT · rohitg00/pro-workflow

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 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 reviewer mralexivy 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. CX Codex ★ 80repo stars qa-reviewer ZaxbyHub The qa-reviewer subagent reviews pull requests before merge, checking logic, security, error handling, style, and test coverage without changing code. CX Codex +1 ★ 539repo stars phase-10b-durable-timeline-re-reviewer ghostwright The phase-10b-durable-timeline-re-reviewer prompt for Claude Code re-audits fixes in Phantom PR #106 Phase 10B, checking durable timelines for secret leaks and validating session resume states. GP ChatGPT ★ 1,497repo stars review owainlewis Runs an isolated read-only code review. It checks changes against specs, probes security flaws, and verifies tests by breaking code deliberately. CX Codex +1 787installs pr-review-cursorrules-prompt-file PatrickJS pr-review-cursorrules-prompt-file — a Cursor rule for focused pull request reviews across security, performance, tests, and architecture, with file-line references and severity labels. CX Codex +1 ★ 41,178repo stars 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 harness-pr-reviewer chrono-meta harness-pr-reviewer — a Claude Code skill that checks a submitted PR against the project's baseline files. It compares the diff with CLAUDE.md, memory files and naming rules, then posts a review comment with a merge recommendation. CX Codex +1 ★ 33repo stars

From the same set83

The whole set →
insights The insights skill turns project memory and session history into analytics on corrections, saved learnings, and coding activity. Ask for a report to spot recurring patterns. CX Codex +1 ★ 2,966repo stars domain-modeling domain-modeling builds the project's shared vocabulary and context boundaries before code gets written, so the agent stops paraphrasing domain terms. Leaves a CONTEXT.md glossary behind. CX Codex +1 ★ 2,966repo stars llm-gate llm-gate configures prompt and agent hooks in Claude Code to validate commit messages, stop dangerous terminal commands, and catch secret leaks before execution. CX Codex +1 ★ 2,966repo stars cost-tracker The cost-tracker skill helps you review Claude Code session costs, set budget checkpoints, and spot expensive work patterns. Use it when planning work across sessions. CX Codex +1 ★ 2,966repo stars skill-conventions skill-conventions defines standards for workflow skills: separates human invocation from auto-triggers, governs state writes, and keeps the skill router in sync. CX Codex +1 ★ 2,966repo stars plan-interrogate The plan-interrogate skill probes a plan before implementation by mapping its decisions and asking about them one at a time. Use it to clarify unresolved design choices. CX Codex +1 ★ 2,966repo stars bug-capture bug-capture is a Claude Code skill that turns reported defects into GitHub issues using the project’s own terms. It activates after a conversational bug report, a QA pass, or a request to file an issue. CX Codex +1 ★ 2,966repo stars context-optimizer context-optimizer controls token consumption and frees context in Claude Code. Use it when agent sessions slow down, forget instructions, or approach budget limits. CX Codex +1 ★ 2,966repo stars

Project sponsors

Companies that keep this analytics open