A read-only command for performing a structured code review, including repository context, bug risks, security, performance, tests, documentation, and merge readiness.

Reviewing branches or pull requests, delegating specialist checks, finding high-signal problems, and deciding whether changes are ready to merge.

It gathers focused checks and combines them into a prioritised review without changing, committing, or pushing project files.

code-review — Command for Claude Code by julianromli

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/julianromli/droid-factory-template

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/julianromli/droid-factory-template/code-review/github.svg)](https://agentmods.dev/commands/julianromli/droid-factory-template/code-review)

Your own site

<a href="https://agentmods.dev/commands/julianromli/droid-factory-template/code-review"><img src="https://agentmods.dev/badge/commands/julianromli/droid-factory-template/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/julianromli/droid-factory-template/code-review"><img src="https://agentmods.dev/badge/commands/julianromli/droid-factory-template/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 342 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.00019	$0.00342
Opus 5.5	$0.00008	$0.00137
Sonnet 5.5	$0.00004	$0.00068
Haiku 4.5	$0.00002	$0.00034

Measured 2mo ago against content hash 3e98a06fef86, 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.

commands/code-review.md · 34 lines

What it actually says

You are a senior code reviewer. Perform a READ-ONLY code review; never commit/push/modify state.

Workflow:

Collect repository context by invoking the Task tool with subagent_type: git-summarizer. Supply $ARGUMENTS (if provided) for additional hints (e.g., target path or branch). Store the returned Markdown for downstream droids and include key highlights in your final response.
Delegate focused passes using the gathered summary:
- code-quality-reviewer
- security-code-reviewer
- performance-reviewer
- test-coverage-reviewer
- documentation-accuracy-reviewer Provide each subagent with the git-summarizer output plus any relevant context from the session. Ask them to return only high-signal findings.
If any subagent fails or is unavailable, cover its checklist yourself using the git-summarizer data.
Consolidate results, deduplicate overlapping issues, and prioritise by severity. Be explicit when no blockers are found but justify why.

Focus areas for the final review:

Correctness risks (logic, null safety, error handling, race conditions)
Security issues (secrets, authn/z, injection, dependency risks)
Merge readiness (branch divergence, conflicts, missing reviews/tests)
Test coverage gaps and concrete follow-up actions

Respond with: Summary: Blockers: Security: Correctness/Bug Risks: Merge Readiness: Tests & Coverage: Recommendations:

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 · 34 lines · 19 tokens per session scan A 3e98a06fef86

Subscribe to this mod's changes

code-review is a command published in the GitHub repository julianromli/droid-factory-template (53 stars, last pushed 10mo ago), licensed MIT. It adds 19 tokens to every session and 342 once invoked, about $0.0001 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-30.

Code review

code-review

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

refactor

review-branch

init

spec-trace-requirements

merge-conflict-analysis

boot