article-icons
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…
Code review closeout for Claude Code, Codex, OpenCode, DeepSeek TUI, and Antigravity CLI: local dirty changes, branch vs main, parallel tests.
$ npx -y skills add smallnest/goal-workflow --skill review-it --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/review-itContext preview
The summary Claude sees to decide when to auto-load this skill.
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 |
请 review 当前 diff。不要只看语法和明显 bug,请重点检查以下维度,最后按严重程度排序:
1. **隐藏副作用 (Hidden Side Effects)** — 变更是否在非显而易见的地方产生级联影响?是否修改了共享状态、全局变量、或外部依赖的行为? 2. **破坏兼容性 (Breaking Compatibility)** — 是否改变了 API 签名、数据结构、配置文件格式、或命令行接口?现有调用方是否会受影响? 3. **边界情况 (Edge Cases)** — null/空值/空集合、极大/极小值、并发/竞态条件、异常路径是否被正确处理? 4. **性能风险 (Performance Risks)** — 是否引入了不必要的循环嵌套、N+1 查询、大对象分配、阻塞 I/O、或锁竞争? 5. **安全风险 (Security Risks)** — 是否存在注入、越权、敏感信息泄露、不安全的反序列化、或依赖版本漏洞? 6. **命名误导 (Naming Misleading)** — 变量/函数/类型名称是否与实际行为不一致?是否存在名不副实或语义模糊的命名? 7. **测试不足 (Insufficient Testing)** — 关键路径、边界条件、错误处理是否缺少测试覆盖?现有测试是否真正验证了期望行为? 8. **未来维护成本 (Future Maintenance Cost)** — 是否引入了不必要的抽象、重复代码、隐式耦合、或难以追踪的控制流?后来者是否容易理解和修改?
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
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:
Bundled helper script for parallel test + review orchestration:
~/.claude/skills/review-it/scripts/review-it --help
The helper:
Include:
Do not run another review solely to improve the final report wording. If review exited clean with no actionable findings, report that as clean.
An AI-driven development workflow — from PRD to shipped code, all within Claude Code.
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…
Reverse-engineer a SPEC document from an existing project. Analyzes code, config, tests, and structure to produce a comprehensive specification. Triggers on:…
Use when turning a requirement, spec, or feature brief into a single self-contained HTML design document in a fixed house style — one styled HTML page with a…
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…
对指定文档进行去 AI 味的改写。自动选择最合适的人性化策略(humanizer-zh / humanize-chinese / technical-writing), 迭代改写直到效果达标或迭代 42 次为止。适用于中文文本的去 AI 化处理,包括通用文章、技术文档、学术论文等。 Use when user…
为任意项目生成 UML 图、架构图和流程图。分析代码库后让用户选择要生成的图表类型,使用 architecture-diagram skill 渲染为 HTML+SVG,保存到 docs/ 目录。适用于任何软件项目的文档可视化。