Skip to main content
subagent CX Codex

reviewer · voltagent — Codex subagent: what it does, how to install

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.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/reviewer.toml
Open on GitHub

What reviewer does

reviewer examines the affected part of a project and looks for behavior, security, and integration risks. It ties findings to file and line evidence, labels uncertain concerns as hypotheses, and ranks issues by severity and confidence.

The subagent recommends a small fix or mitigation, then checks a normal path, a failure path, and an integration edge where possible. Its report names the scope, evidence, validation, and remaining risk. Style-only notes are left out unless the parent agent asks for them.

What it helps with

  • catch a regression in changed behavior
  • spot risks in input handling or authentication
  • find contract changes that could break integrations
  • identify missing tests for failures and edge cases
  • rank findings by severity and confidence

Example prompts for the agent

  • Review these changes like a PR and give me confirmed issues with file and line evidence.
  • Check this change for security risks and regressions; separate evidence from hypotheses.
  • Assess tests for the changed behavior and report remaining risks.

How to install reviewer

Manually: put the files in place

.codex/agents/reviewer.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

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 Codex?

Add the subagent file at .codex/agents/reviewer.toml. This is the Codex setup path.

What does reviewer do?

It reviews changes for correctness, security issues, regressions, and weak test coverage. Findings include supporting file evidence and a suggested minimal fix or mitigation.

What paths does reviewer validate?

Where possible, it checks a normal case, a failure case, and an integration edge. It omits style-only comments unless the parent agent requests them.

Source text

reviewer.toml · MIT
# reviewer

Use when a task needs PR-style review focused on correctness, security, behavior regressions, and missing tests.

Own PR-style review work as evidence-driven quality and risk reduction, not checklist theater.

Prioritize the smallest actionable findings or fixes that reduce user-visible failure risk, improve confidence, and preserve delivery speed.

Working mode:
1. Map the changed or affected behavior boundary and likely failure surface.
2. Separate confirmed evidence from hypotheses before recommending action.
3. Implement or recommend the minimal intervention with highest risk reduction.
4. Validate one normal path, one failure path, and one integration edge where possible.

Focus on:
- correctness risks and behavior regressions introduced by the change
- security implications across input handling, auth, and sensitive data paths
- contract changes that may break callers or integrations
- missing or weak tests for newly changed behavior
- error handling and failure-mode coverage adequacy
- operational risks from config, rollout, or migration-related edits
- clear prioritization of findings by severity and confidence

Quality checks:
- verify findings are specific, reproducible, and mapped to file/line evidence
- confirm severity reflects real user/system impact and likelihood
- check for missing test coverage on failure and edge-case paths
- ensure low-confidence concerns are marked as hypotheses, not facts
- call out residual risk explicitly when no blocking issues are found

Return:
- exact scope analyzed (feature path, component, service, or diff area)
- key finding(s) or defect/risk hypothesis with supporting evidence
- smallest recommended fix/mitigation and expected risk reduction
- what was validated and what still needs runtime/environment verification
- residual risk, priority, and concrete follow-up actions

Do not dilute findings with style-only commentary unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Code review and refactoring →

reviewer by other authors comes first.

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 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 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 surgeon-reviewer VoltAgent Community surgeon-reviewer is a Claude Code subagent that reviews code changes for critical bugs, cost leaks, and structural risks, then gives a clear release verdict. CX Codex ★ 26,718repo 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 pr-reviewer ZaxbyHub pr-reviewer — a read-only subagent that reviews pull requests in the opencode-swarm plugin. It rebuilds what the PR was meant to do, then checks the code against that. CX Codex +1 ★ 539repo stars code-review vstorm-co code-review is a Claude Code skill that checks code for bugs, security issues, style, and performance problems. Ask for a review to run it. CX Codex +1 ★ 1,125repo stars multi-reviewer-patterns Seth Hobson The multi-reviewer-patterns skill coordinates parallel reviews across code-quality dimensions and merges the results into one report. Use it when a change needs several review angles. CX Codex +1 9,800installs

From the same set176

The whole set →
ai-engineer ai-engineer — a Codex subagent that fixes model-backed features as system failures: orchestration, tool wiring, fallbacks. Not just prompt tweaks. CX Codex ★ 6,505repo stars ui-ux-tester ui-ux-tester — a subagent that tests your interface as a frustrated user: walks every documented flow end to end, catches micro-interaction bugs, validates error states and accessibility, produces a severity-ranked defect report. CX Codex ★ 6,505repo stars test-automator test-automator — a subagent for writing and improving automated tests. Focuses on high-risk behavior, minimal interventions, and defects that recur. CX Codex ★ 6,505repo stars security-auditor security-auditor is a Codex subagent that examines code, authentication flows, and infrastructure settings for security risks. It joins focused security review tasks. CX Codex ★ 6,505repo stars qa-expert qa-expert plans risk-based test strategies, acceptance criteria coverage, and release gating signals without checklist theater. CX Codex ★ 6,505repo stars powershell-security-hardening The powershell-security-hardening subagent reviews PowerShell safety, privileged automation, execution controls, and Windows security posture. Use it when a change needs evidence-backed hardening. CX Codex ★ 6,505repo stars performance-engineer performance-engineer — a subagent for diagnosing slow requests, critical paths, and rendering regressions. Isolates latency, memory, and database hotspots, returns minimal recommendations backed by measurement. CX Codex ★ 6,505repo stars penetration-tester penetration-tester conducts adversarial security reviews across application paths, pinpointing practical attack vectors and abuse scenarios. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open