A thorough check of a file, branch, or set of code changes for correctness, edge cases, security, performance, tests, and maintainability.

Use it to review a specific file, compare a branch with the main branch, or inspect staged or unstaged changes.

A code review can catch problems that automated checks miss, such as unsafe behavior, missing error handling, or untested failure cases.

review — Command for Claude Code by boparaiamrit

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/boparaiamrit/skills-by-amrit

Made for: Claude Code.

Or install skills-by-amrit, the plugin that ships this one along with the rest of its 33 skills, 34 commands, 9 agents.

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/boparaiamrit/skills-by-amrit/review/github.svg)](https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/review)

Your own site

<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/review"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/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/boparaiamrit/skills-by-amrit/review"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 437 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.00015	$0.00437
Opus 5	$0.00008	$0.00218
Sonnet 5	$0.00003	$0.00087
Haiku 4.5	$0.00002	$0.00044

Measured 11d ago against content hash 7c86e55d4871, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

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 11d 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/review.md · 50 lines

What it actually says

/review — Code Review

Review code changes for quality, correctness, and best practices.

Instructions

Determine scope:
- If $ARGUMENTS is a file path → review that specific file
- If $ARGUMENTS is a branch name → review git diff main..$ARGUMENTS
- If empty → review git diff --staged (staged changes)
- If no staged changes → review git diff (unstaged changes)
Review Checklist — Check each change for:
- Correctness: Does the logic do what it claims?
- Edge cases: Are boundary conditions handled?
- Error handling: Are errors caught and handled properly?
- Security: Any injection, auth bypass, or data exposure?
- Performance: Any N+1 queries, unnecessary loops, or missing indexes?
- Tests: Are there tests? Do they cover the happy path AND error cases?
- Naming: Are variables, functions, and files named clearly?
- DRY: Is there duplicated logic that should be extracted?
- Types: Are type hints/annotations present and correct?

Output format:

## Code Review — [scope]

### ✅ Looks Good
- [List things done well]

### 🔧 Suggestions
- [Improvements that should be made]

### ⚠️ Issues
- [Problems that must be fixed before merge]

### 📝 Nits
- [Minor style/formatting preferences]

Be specific — reference exact file paths and line numbers.
Be constructive — explain WHY something is an issue, not just WHAT.

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.

11d ago First seen · 50 lines · 15 tokens per session scan A 7c86e55d4871

Subscribe to this mod's changes

review is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 437 once invoked, about $0.0001 per session on Opus 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

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

/review — Code Review

Instructions

What this file has done since we first saw it

Other commands, from other repositories

sdd-init

review-branch

init

merge-conflict-analysis

repo-audit

argos