跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 review-it

Review It

代码审查关闭 Claude Code, Codex, OpenCode, DeepSeek TUI, 和 Antigravity CLI: 局部脏变,分支对主,平行测试.

459 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

代码审查关闭 Claude Code, Codex, OpenCode, DeepSeek TUI, 和 Antigravity CLI: 局部脏变,分支对主,平行测试.

何时用

- 用户要求代码审查/审查-it/自动审查

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:CC Review、Supported Agents、Contract、Review Focus、Pick Target、Claude Code / OpenCode / DeepSeek TUI。

文件分析

文件分析:除 SKILL.md 外,正文引用了 scripts/review-it,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Code review closeout for Claude Code, Codex, OpenCode, DeepSeek TUI, and Antigravity CLI: local dirty changes, branch vs main, parallel tests.

CC ReviewSupported AgentsContractReview FocusPick TargetClaude Code / OpenCode / DeepSeek TUIAntigravity CLI (`agy`)CodexReview uncommitted changesReview branch diffParallel CloseoutUncommitted vs Branch Review

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
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.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 1
  • scripts/review-it

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「review-it」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-ec660095b23391de-%E5%AE%A1%E6%9F%A5.html
请存为 .cursor/skills/review-it/SKILL.md 或 .claude/skills/review-it/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/smallnest/goal-workflow 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/smallnest/goal-workflow' --list

npx skills add 'https://github.com/smallnest/goal-workflow' --skill 'review-it'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- 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." --- # CC Review Run automated code review as a closeout check before committing or shipping. Works across multiple AI coding agents. Use when: - user asks for code review / review-it / autoreview - after non-trivial code edits, before final/commit/ship - reviewing a local branch or PR branch after fixes ## Supported Agents | 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 | ## Contract - Treat review output as advisory. Never blindly apply it. - Verify every finding by reading the real code path and adjacent files. - Read dependency docs/source/types when the finding depends on external behavior. - Reject unrealistic edge cases, speculative risks, broad rewrites, and fixes that over-complicate the codebase. - Prefer small fixes at the right ownership boundary; no refactor unless it clearly improves the bug class. - Keep going until review returns no accepted/actionable findings. - If a review-triggered fix changes code, rerun focused tests and rerun review. - Stop as soon as the review comes back clean with no actionable findings. - If rejecting a finding as intentional/not worth fixing, add a brief inline code comment only when it explains a real invariant or ownership decision that future reviewers should know. - Do not push just to review. Push only when the user requested push/ship/PR update. ## Review Focus 请 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)** — 是否引入了不必要的抽象、重复代码、隐式耦合、或难以追踪的控制流?后来者是否容易理解和修改? ## Pick Target ### Claude Code / OpenCode / DeepSeek TUI 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: ```bash 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: ```bash base=$(gh pr view --json baseRefName --jq .baseRefName) git diff "origin/$base"...HEAD > /tmp/review-it.diff ``` ### Antigravity CLI (`agy`) Dirty local work: ``` /code-review ``` Branch/PR work — review all changes against base: ```bash 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: ```bash base=$(gh pr view --json baseRefName --jq .baseRefName) git diff "origin/$base"...HEAD > /tmp/review-it.diff ``` ### Codex ```bash # Review uncommitted changes codex review # Review branch diff git diff origin/main...HEAD > /tmp/review-it.diff codex review /tmp/review-it.diff ``` ## Parallel Closeout Format first if formatting can change line locations. Then it's OK to run tests and review in parallel: ```bash scripts/review-it --parallel-tests "" ``` 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. ## Uncommitted vs Branch Review Choose the right mode: - **Uncommitted changes** (staged/unstaged): use `/review` directly (Antigravity: `/code-review`, Codex: `codex review`) - **Committed, not pushed**: use `git diff origin/main...HEAD` + review - **Pushed/PR**: same as committed, against the PR base - **Clean working tree**: skip review if there's truly nothing to review ## Helper Bundled helper script for parallel test + review orchestration: ```bash ~/.claude/skills/review-it/scripts/review-it --help ``` The helper: - Detects which agent is running (Claude Code, Antigravity CLI, Codex) via `--agent auto` - Detects whether to use uncommitted review or branch diff review - For branch mode: generates diff against `origin/main` (or PR base), then triggers review - Supports `--parallel-tests` for concurrent test + review execution - Supports `--dry-run` for checking what command would be used - Prints `review-it clean: no accepted/actionable findings reported` when review is clean ## Final Report Include: - review target (uncommitted / branch / PR base) - tests/proof run - findings accepted/rejected, briefly why - the clean review result, or why a remaining finding was consciously rejected Do not run another review solely to improve the final report wording. If review exited clean with no actionable findings, report that as clean.

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…