A command that reviews the current Git changes as if an independent developer wrote them.

Use it before merging code to get specific findings with file locations, explanations, and concrete fixes, or confirmation that the changes are sound.

It focuses attention on correctness bugs, race conditions, missed requirements, and unrelated changes instead of style preferences.

code-review — Command for Claude Code by iberant

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/iberant/iberant-ai-starter-kit

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/iberant/iberant-ai-starter-kit/code-review/github.svg)](https://agentmods.dev/commands/iberant/iberant-ai-starter-kit/code-review)

Your own site

<a href="https://agentmods.dev/commands/iberant/iberant-ai-starter-kit/code-review"><img src="https://agentmods.dev/badge/commands/iberant/iberant-ai-starter-kit/code-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/iberant/iberant-ai-starter-kit/code-review"><img src="https://agentmods.dev/badge/commands/iberant/iberant-ai-starter-kit/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 151 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00011	$0.00151
Opus 5.5	$0.00004	$0.00060
Sonnet 5.5	$0.00002	$0.00030
Haiku 4.5	$0.00001	$0.00015

Measured 2mo ago against content hash 2101555f6e0a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

templates/.claude/commands/code-review.md · 17 lines

What it actually says

Review the current git diff as an independent reviewer who did NOT write this code.

Focus, in order:

Correctness bugs, race conditions, and unhandled error/edge cases.
Whether every requirement in the plan/spec is actually implemented.
Anything changed outside the task's stated scope.

Report only findings that affect correctness or the stated requirements — not style preferences (those are the linter's job). For each finding give file:line, the problem, and a concrete fix. If the diff is sound, say so plainly.

Tip: the bundled /code-review skill runs this in a fresh subagent; prefer it when available.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 17 lines · 11 tokens per session scan A 2101555f6e0a

Subscribe to this mod's changes

code-review is a command published in the GitHub repository iberant/iberant-ai-starter-kit (5 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 151 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review

code-review next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
code-reviewiberant/iberant-ai-starter-kit	Command	5	4mo ago	MIT	A	11	Claude Code
diff-reviewcoco-research/coco	Command	785	yesterday	Apache-2.0	A	11	Claude Code
review-branchdamusix/atomic-claude	Command	115	5d ago	MIT	A	35	Claude Code
refactorRchGrav/claudebox	Command	1.2k	1mo ago	MIT	A	9	Claude Code
spec-trace-requirementsrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
merge-conflict-analysisrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
initazrtydxb/procoder	Command	211	11d ago	Apache-2.0	A	16	Claude Code