full-review

A command that reviews a project in three areas at the same time: code quality, security, and whether the documentation matches the code.

In plain words
What is it for?
Use it on changed files, a chosen path, or the whole current directory to find bugs, readability and performance problems, security risks, exposed secrets, and outdated or incomplete documentation.
Why use it?
It gathers several kinds of review in one run and combines the results, so you do not need to perform separate checks or compare separate reports yourself.

Command

Part of the claude-code-dotfiles plugin — 3 skills, 4 commands, 5 agents, 1 plugin shipped together

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/full-review
Clone the repo
git clone --depth 1 https://github.com/flasherses/claude-code-dotfiles

Or install claude-code-dotfiles, the plugin that ships this one along with the rest of its 3 skills, 4 commands, 5 agents, 1 plugin.

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 982 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.00982
Opus 5 $0.00000 $0.00491
Sonnet 5 $0.00000 $0.00196
Haiku 4.5 $0.00000 $0.00098

Measured 3d ago against content hash 215ad5a22d32, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

full-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 3d 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/full-review.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/full-review — 并行全量审查

对当前项目执行并行全量审查:代码质量 + 安全审计 + 文档一致性,三个 agent 同时跑,最后汇总。

用法

/full-review [目标路径]

不指定路径时,审查 git diff 中所有变更文件。无 git 仓库时审查整个当前目录。

执行模式:并行分派(Parallel Dispatch)

/review 的区别:/review 顺序执行(先 reviewer 再 auditor),/full-review 同时启动三个 agent。

/full-review
    │
    ├──→ code-reviewer   (background) ──→ 代码质量报告
    ├──→ security-auditor (background) ──→ 安全审计报告
    └──→ doc-explorer     (background) ──→ 文档一致性报告
            │
            └──→ 全部完成 → 汇总 → 交叉分析

执行流程

阶段 1: Decompose(拆解)

确定审查范围的变更文件列表:

git diff --name-only HEAD 2>$null
# 或用户指定的路径

将审查拆为三个独立维度:

维度 Agent 关注点
代码质量 code-reviewer Bug、命名、性能、可读性
安全漏洞 security-auditor OWASP、密钥泄露、注入
文档一致 doc-explorer 代码与文档同步、注释完整性

阶段 2: Dispatch(并行分派)

关键:在同一轮中使用 run_in_background: true,同时启动三个 agent。

Agent: code-reviewer (background)
  Prompt: "Review the following changed files for bugs, code quality, and performance issues:
           [changed files list from phase 1]"

Agent: security-auditor (background)
  Prompt: "Audit the following changed files for OWASP Top-10 vulnerabilities, 
           exposed secrets, and unsafe patterns: [changed files list]"

Agent: doc-explorer (background)
  Prompt: "Check if the following changed files have adequate documentation,
           comments, and if any related docs need updating: [changed files list]"

三个 agent 同时执行,互不依赖。收到各自完成通知后进入阶段 3。

阶段 3: Collect(收集)

每个 agent 完成后返回结构化报告。收集三个报告的 key findings。

阶段 4: Consolidate(汇总 + 交叉分析)

将三个报告合并,重点做交叉分析——同一段代码在不同维度上的问题:

## 并行全量审查报告

### 审查范围
- 变更文件: [N] 个
- 执行时间: [并行耗时]
- Agent: code-reviewer + security-auditor + doc-explorer

### 交叉分析(同一代码的多维度问题)

| 文件:行 | 代码质量 | 安全 | 文档 | 综合判断 |
|----------|----------|------|------|----------|
| `auth.py:23` | Warning: 复杂度过高 | Critical: SQL 注入 | Info: 缺 docstring | **必须修** |
| `utils.py:45` | Suggestion: 命名模糊 | — | Warning: 行为未注释 | 建议修 |

### 各维度汇总

#### 代码质量 (code-reviewer)
- Critical: [N], Warnings: [N], Suggestions: [N]
- [关键发现摘要]

#### 安全审计 (security-auditor)
- 风险等级: LOW / MEDIUM / HIGH / CRITICAL
- [关键发现摘要]

#### 文档一致性 (doc-explorer)
- [关键发现摘要]

### 总体评估
- 综合评级: PASS / NEEDS FIXES / DO NOT MERGE
- 必须修: [N] 项
- 建议修: [N] 项

### Top 3 优先修复
1. [最严重问题 — 含文件和行号]
2. [次严重问题 — 含文件和行号]
3. [第三严重 — 含文件和行号]

Read the full file on GitHub · 110 lines

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. 3d ago First seen · 110 lines · 0 tokens per session scan A 215ad5a22d32

Subscribe to this mod's changes

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