with one click
review-it
// Code review closeout for Claude Code, Codex, OpenCode, DeepSeek TUI, and Antigravity CLI: local dirty changes, branch vs main, parallel tests.
// Code review closeout for Claude Code, Codex, OpenCode, DeepSeek TUI, and Antigravity CLI: local dirty changes, branch vs main, parallel tests.
| name | review-it |
| description | Code review closeout for Claude Code, Codex, OpenCode, DeepSeek TUI, and Antigravity CLI: local dirty changes, branch vs main, parallel tests. |
Run automated code review as a closeout check before committing or shipping. Works across multiple AI coding agents.
Use when:
| Agent | Review Command | Notes |
|---|---|---|
| Claude Code | /review | Built-in, works on uncommitted changes or diff |
| Codex | codex review | Pass diff file or let it auto-detect |
| OpenCode | /review | Same as Claude Code |
| DeepSeek TUI | /review or manual diff review | Pass diff content for analysis |
| Antigravity CLI | /code-review | Built-in slash command, auto-detects diff |
Dirty local work (default — /review works on uncommitted changes):
/review
Branch/PR work — review all changes against base:
First generate a diff, then review it:
git diff origin/main...HEAD > /tmp/review-it.diff
Then review the diff file with a focused prompt:
/review the changes in /tmp/review-it.diff against origin/main
If an open PR exists, use its actual base:
base=$(gh pr view --json baseRefName --jq .baseRefName)
git diff "origin/$base"...HEAD > /tmp/review-it.diff
agy)Dirty local work:
/code-review
Branch/PR work — review all changes against base:
git diff origin/main...HEAD > /tmp/review-it.diff
Then pass the diff to the review command:
/code-review the changes in /tmp/review-it.diff against origin/main
If an open PR exists, use its actual base:
base=$(gh pr view --json baseRefName --jq .baseRefName)
git diff "origin/$base"...HEAD > /tmp/review-it.diff
# Review uncommitted changes
codex review
# Review branch diff
git diff origin/main...HEAD > /tmp/review-it.diff
codex review /tmp/review-it.diff
Format first if formatting can change line locations. Then it's OK to run tests and review in parallel:
scripts/review-it --parallel-tests "<focused test command>"
Tradeoff: tests may force code changes that stale the review. If tests or review lead to code edits, rerun the affected tests and rerun review until no accepted/actionable findings remain.
Choose the right mode:
/review directly (Antigravity: /code-review, Codex: codex review)git diff origin/main...HEAD + reviewBundled helper script for parallel test + review orchestration:
~/.claude/skills/review-it/scripts/review-it --help
The helper:
--agent autoorigin/main (or PR base), then triggers review--parallel-tests for concurrent test + review execution--dry-run for checking what command would be usedreview-it clean: no accepted/actionable findings reported when review is cleanInclude:
Do not run another review solely to improve the final report wording. If review exited clean with no actionable findings, report that as clean.
Detect software architecture bad smells, algorithmic complexity hotspots, and anti-patterns in a codebase. Produces a detailed markdown report identifying violations of architectural principles, design patterns, code quality, and performance complexity. Triggers on: smell, code smell, architecture smell, find anti-patterns, detect bad smells, complexity analysis, 代码坏味道, 架构坏味道, 反模式, 找出坏味道, 复杂度分析.
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. After PRD is confirmed, use /prd-to-spec (optional) for technical design, then /to-issues to create implementable tickets. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out, 写PRD, 需求文档, 需求分析, 规格说明.
Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe). Use after /prd (and optionally /prd-to-spec) to turn requirements into actionable tickets. Triggers on: create issues, to-issues, 创建issue, 拆解issue, 生成卡片, 创建卡片, generate issues from PRD, issues from spec.
Transform a PRD into a technical SPEC document — architecture, API design, data model, error handling, and implementation contracts. Triggers on: prd-to-spec, prd to spec, prd转spec, 需求转设计, 需求转规格, generate spec from prd, design from prd, 技术方案, 设计方案.
Reverse-engineer a SPEC document from an existing project. Analyzes code, config, tests, and structure to produce a comprehensive specification. Triggers on: code-to-spec, reverse spec, generate spec, 逆向规格, 生成规格文档, 生成设计文档, 生成设计方案, extract spec, document this project, what does this project do.
Capture implementation notes after code implementation and review/fix. Records design decisions, deviations, tradeoffs, and open questions to docs/issue#XXXX.html. Triggers on: /note-it, 记录笔记, implementation notes.