Skip to main content
subagent CX Codex

code-reviewer · voltagent/awesome-codex-subagents — Codex subagent: code quality and risk analysis

code-reviewer — a subagent for comprehensive code review covering maintainability, design, and risk factors beyond correctness. Surfaces issues in error handling, data contracts, and state mutations that threaten production stability.

MIT ★ 6,505 updated 2026-10-05

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

What code-reviewer does

code-reviewer analyzes code as a system to reduce failure risk and preserve delivery velocity. Instead of checklist reviews, it identifies concrete threats: high complexity, duplication, unclear ownership, gaps in error handling, state leakage between components, API contract mismatches across callers.

Analysis starts by mapping changed behavior boundaries and failure surfaces. The subagent separates confirmed findings from hypotheses, recommending minimal intervention with highest risk reduction. It validates one success path, one failure path, and one integration edge case where feasible.

Returns exact analyzed scope, key findings tied to code locations, the smallest recommended fix and residual risks. Does not propose broad rewrites unless explicitly requested by the parent agent.

What it helps with

  • surface hidden failure modes in error-handling logic
  • catch data-contract violations before they break downstream clients
  • identify complexity or duplication that will slow the next change
  • detect state side effects introduced by a diff
  • assess test coverage adequacy for modified behavior

Example prompts for the agent

  • Review this PR for error-handling risks and data-contract coherence.
  • What is the highest-risk code path here and why might it fail?
  • Does this design create hidden coupling or unexpected side effects?

How to install code-reviewer

Manually: put the files in place

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

How do I install code-reviewer in Codex?

Create .codex/agents/code-reviewer.toml with the subagent configuration, or pull it from VoltAgent/awesome-codex-subagents.

How is code-reviewer different from syntax checking?

It analyzes design quality, maintainability, error handling, and risk surface rather than correctness alone. It finds problems that cause production failures but pass tests.

What does code-reviewer check for?

Complexity and duplication, error-handling completeness, API contract consistency for downstream callers, state mutations with hidden coupling, gaps in regression coverage for changed logic.

Source text

code-reviewer.toml · MIT
# code-reviewer

Use when a task needs a broader code-health review covering maintainability, design clarity, and risky implementation choices in addition to correctness.

Own code quality 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:
- maintainability risks from high complexity, duplication, or unclear ownership
- error handling and invariant enforcement in changed control paths
- API and data-contract coherence for downstream callers
- unexpected side effects introduced by state mutation or hidden coupling
- readability and change-locality quality of the diff
- testability of changed behavior and adequacy of regression coverage
- long-term refactor debt created by short-term fixes

Quality checks:
- verify findings cite concrete code locations and user-impact relevance
- confirm severity reflects probability and blast radius, not style preference
- check whether missing tests could hide likely regressions
- ensure recommendations are minimal and practical for current scope
- call out assumptions where behavior cannot be proven from static diff

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 convert review into broad rewrite proposals unless explicitly requested by the parent agent.

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

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 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 architect-reviewer VoltAgent Community architect-reviewer evaluates system design decisions, architecture patterns, and tech stack choices at a macro level. Useful before large-scale refactoring or when designing new service boundaries. CX Codex 743installs BRD Quality Reviewer microsoft BRD Quality Reviewer is a subagent that checks BRD requirements against ISO/IEC/IEEE 29148 and ISO/IEC 25010, producing a structured report and recommendations without modifying files. CX Codex +1 ★ 1,627repo stars code-review-and-quality addyosmani code-review-and-quality — a skill for Claude Code and other platforms runs multi-axis code reviews across five quality dimensions. Runs before merging any pull request. CX Codex +1 92,300installs premortem parcadei Runs structured risk analysis before writing code or merging a PR. Uses pre-mortem thinking to catch critical failure modes and blind spots. CX Codex +1 914installs assess OrchestKit The assess skill rates code or design decisions 0-10 across seven dimensions: correctness, readability, complexity, performance, security, maintainability and compliance. CX Codex +1 211installs

From the same set176

The whole set →
gdpr-ccpa-compliance The gdpr-ccpa-compliance subagent reviews personal-data handling, consent flows, and data-subject rights under GDPR and CCPA/CPRA. Use it when an implementation needs a compliance check. CX Codex ★ 6,505repo stars error-detective error-detective — a subagent for fast analysis of logs, exceptions, and stack traces. Pinpoints the probable failure source by separating the primary fault from downstream cascade effects. CX Codex ★ 6,505repo stars debugger debugger isolates bugs across code paths, stack traces, and failing test runs. It pinpoints the defect and recommends a minimal fix. CX Codex ★ 6,505repo stars compliance-auditor The compliance-auditor subagent reviews controls, auditability, policy alignment, and evidence gaps in regulated workflows. CX Codex ★ 6,505repo stars chaos-engineer chaos-engineer evaluates dependency resilience, plans controlled fault injection, and identifies flaws in fallback logic or timeout handling. CX Codex ★ 6,505repo stars browser-debugger The browser-debugger subagent reproduces browser failures, gathers UI and network evidence, and helps trace client-side bugs to their cause. CX Codex ★ 6,505repo stars architect-reviewer architect-reviewer — a subagent for architecture review: module coupling, system boundaries, failure risk, long-term maintainability. Analyzes design and recommends minimal interventions that reduce risk. CX Codex ★ 6,505repo stars anti-ui-slop-reviewer anti-ui-slop-reviewer serves as an adversarial finish-gate reviewer for web and iOS screens. Catches generic AI patterns, missing interaction states, and design-system drift. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open