review

A code-review command that examines specified files or the current Git changes and reports security, logic, quality, and performance issues.

In plain words
What is it for?
Use `/review` with a file or directory, or without a path to review Git changes, then receive issue counts and an overall merge recommendation.
Why use it?
It turns a code review into a consistent process and adds a security audit for sensitive files such as authentication, database, and configuration code.

Command

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.

agentmods
npx agentmods add commands/flasherses/claude-code-dotfiles/review
Clone the repo
git clone --depth 1 https://github.com/flasherses/claude-code-dotfiles
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 319 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00319
Opus 5 $0.00000 $0.00160
Sonnet 5 $0.00000 $0.00064
Haiku 4.5 $0.00000 $0.00032

Measured 2d ago against content hash 33d566df9ef9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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 · 36 lines

What it actually says

/review — 代码审查

对指定文件或最近变更执行全流程代码审查。

用法

/review [文件或目录路径]

不指定路径时,审查 git diff 中所有变更文件。

执行流程

  1. 确定审查范围

    • 如果提供了 $ARGUMENTS,审查指定文件
    • 如果未提供参数,运行 git diff --name-only 获取变更文件列表
    • 如果不在 git 仓库中,提示用户指定文件
  2. 代码审查 — 调起 code-reviewer 子代理逐文件审查

    • 关注:安全漏洞、逻辑错误、代码质量、性能问题
  3. 安全审计(如涉及以下文件类型自动触发)

    • 配置文件(.json, .yaml, .env, .toml
    • 认证相关代码(auth, login, session, token
    • 数据库操作代码(sql, query, migrate
    • 调起 security-auditor 子代理
  4. 汇总报告 — 合并 reviewer 和 auditor 的输出,给出总体评估

输出

  • 审查文件数
  • 问题汇总:Critical / Warning / Suggestion 各多少
  • 整体评估:PASS / NEEDS FIXES / DO NOT MERGE
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.

  1. 2d ago First seen · 36 lines · 0 tokens per session scan A 33d566df9ef9

Subscribe to this mod's changes

review is a command published in the GitHub repository flasherses/claude-code-dotfiles (5 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 319 tokens. 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.