一键导入
review-it
Code review closeout for Claude Code, Codex, OpenCode, DeepSeek TUI, and Antigravity CLI: local dirty changes, branch vs main, parallel tests.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Code review closeout for Claude Code, Codex, OpenCode, DeepSeek TUI, and Antigravity CLI: local dirty changes, branch vs main, parallel tests.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Graph engineering for parallel task execution: convert a task, PRD, SPEC, or issue set into a dependency graph (DAG), layer it into supersteps, then implement each independent node concurrently with subagents — each node runs /goal → /review-it → /ship-it in an isolated git worktree, with a fan-in barrier between waves. Triggers on: graph, graph engineering, build a graph, task graph, dependency graph, DAG, parallel implement, 并发实现, 并行实现, 任务图, 把任务变成图, fan-out fan-in, superstep, dynamic workflow.
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, 需求文档, 需求分析, 规格说明.
Modernize Go code by applying version-appropriate idioms and APIs (gofix-style transformations). Scans go.mod for the Go version, then transforms Go source files to use modern patterns—from Go 1.0 through 1.26+. Use when the user says "现代化","现代Go语言", "地道的", "idiomatic", "modernize", "modern-go", "update Go code", "gofix", or wants to upgrade Go idioms.
Illustrate an article (Markdown, HTML, etc.) with animated-style icons from itshover.com/icons. Fetches icons as clean inline SVG and places them at section headings, key concepts, lists, and callouts. Triggers on: /article-icons, 配图, 给文章配图标, add icons to article, illustrate with icons.
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 design document (design proposal) from a PRD, in the style of Go's official design proposals — Abstract / Background / Design / Rationale / Compatibility / Implementation, heavy on the 'why' and tradeoffs. Triggers on: to-design, prd-to-design, prd转设计文档, 生成设计文档, 写设计文档, design doc, design proposal, 设计提案, 技术设计文档.
| 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 |
请 review 当前 diff。不要只看语法和明显 bug,请重点检查以下维度,最后按严重程度排序:
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.