跳到主内容
智客 ZICQ

技能库 智客分类:安全测试 open-code-review

Open Code Review

使用`ocr' CLI从alibaba/开放码-审查对Git更改进行AI-能动代码审查。 当用户要求审查代码,审查拉出请求,审查阶段/未阶段的更改,审查承诺,或比较分支处理代码质量问题时使用. 产生行级审查评论,在接到请求时可以自动应用修正. 通过适当的审查规则,可以发现各种类型的问题,包括错误、安全弱点、性能问题和代码质量问题.

5560 安装量

官方网址:作者主页

技能介绍

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

做什么

使用 alibaba/ 开放式代码审查的“ ocr” CLI 对 Git 修改进行 AI 授权代码审查

何时用

用户要求审查代码,审查拉动请求,审查阶段/未完成的修改,审查承诺,或比较代码质量问题的分支。 产生行级审查评论,在接到请求时可以自动应用修正. 有了适当的审查规则,就能发现Vario

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Open Code Review、Workflow、Step 1: Gather Business Context、Step 2: Run Code Review、Step 3: Report、Step 4: Fix。 其中含规范建议的小节:分步指令。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Performs AI-powered code review on Git changes using the `ocr` CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply fixes when requested. With appropriate review rules, can detect various types of issues including bugs, security vulnerabilities, performance problems, and code quality concerns.

Open Code ReviewWorkflowStep 1: Gather Business ContextStep 2: Run Code ReviewStep 3: ReportStep 4: FixOutput FormatCode Review ResultsCriticalHighMediumCustom Review Rules

兼容:Requires the `ocr` CLI installed (via `npm install -g @alibaba-group/open-code-review` or GitHub release binary). Requires a configured LLM (Anthropic or OpenAI-compatible) before first run. · 许可:Apache-2.0

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
open-code-review
description
Performs AI-powered code review on Git changes using the `ocr` CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply fixes when requested. With appropriate review rules, can detect various types of issues including bugs, security vulnerabilities, performance problems, and code quality concerns.
compatibility
Requires the `ocr` CLI installed (via `npm install -g @alibaba-group/open-code-review` or GitHub release binary). Requires a configured LLM (Anthropic or OpenAI-compatible) before first run.
许可
Apache-2.0
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

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

安装这个技能

Skills CLI ↗

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

交给 Agent 安装

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

把 Agent Skill「open-code-review」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-6ddd454be1ce548a-%E6%89%93%E5%BC%80%E4%BB%A3%E7%A0%81%E5%AE%A1%E6%9F%A5.html
请存为 .cursor/skills/open-code-review/SKILL.md 或 .claude/skills/open-code-review/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

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

npx skills add 'https://github.com/alibaba/open-code-review' --list

npx skills add 'https://github.com/alibaba/open-code-review' --skill 'open-code-review'

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

阅读排版
--- name: open-code-review description: > Performs AI-powered code review on Git changes using the `ocr` CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply fixes when requested. With appropriate review rules, can detect various types of issues including bugs, security vulnerabilities, performance problems, and code quality concerns. license: Apache-2.0 compatibility: > Requires the `ocr` CLI installed (via `npm install -g @alibaba-group/open-code-review` or GitHub release binary). Requires a configured LLM (Anthropic or OpenAI-compatible) before first run. metadata: author: alibaba homepage: https://github.com/alibaba/open-code-review version: "1.0.0" --- # Open Code Review A skill for invoking [open-code-review](https://github.com/alibaba/open-code-review) (`ocr`) — an open-source AI code review CLI that reads Git diffs and generates structured, line-level review comments. ## Workflow ### Step 1: Gather Business Context Analyze the review target (commits, branch, or changes) to extract concise business context. Pass this context via `--background` to improve review quality. ### Step 2: Run Code Review Run the OCR command with appropriate flags. **Always pass business context via `--background`** when available: ```bash ocr review --audience agent --background "business context here" [user-args] ``` **Argument handling:** - **Background context** (RECOMMENDED): use `--background "context"` or `-b "context"` to provide business context for better review quality - **Default** (no user arguments): reviews staged, unstaged, and untracked changes (workspace mode) - **Specific commit**: use `--commit` or `-c` to review a single commit against its parent - **Branch comparison**: use `--from ` and `--to ` to review diff between two refs - **Timeout**: effective timeout per review group = `--timeout` × review rounds. Default `--timeout 15` with default effort `medium` (2 rounds) gives 30 minutes; `low`/`high` give 15/45 minutes. - **Concurrency**: default concurrency is 8 file workers; reduce with `--concurrency ` if rate limits are hit - **Preview mode**: use `--preview` or `-p` to preview which files will be reviewed without running the LLM - **Output file**: use `--output ` to write the full result to a file instead of stdout. If the command fails with `unknown flag: --output`, do not continue the review with plain stdout. Ask the user whether to upgrade (`npm i -g @alibaba-group/open-code-review@latest`) and wait for the answer before proceeding. After the user confirms and the upgrade succeeds, rerun with `--output`. - **Installation**: if `ocr` command is not found, install it by running `npm i -g @alibaba-group/open-code-review` **Common invocation patterns:** | User says | Command to run | |-----------|---------------| | "review my changes" / "review the working copy" | `ocr review --audience agent -b "context"` | | "review this PR" / "review feature branch" | `ocr review --audience agent -b "context" --from main --to ` | | "review commit abc123" | `ocr review --audience agent -b "context" --commit abc123` | | "what would be reviewed?" (dry-run) | `ocr review --preview` | **Output mode:** - Always use `--audience agent` to suppress progress UI and emit only the final summary - **Prevent output truncation**: For large reviews or restricted tool environments, pass `--output /tmp/ocr_out.txt` and inspect the file in full via a file reading tool instead of piping stdout through `tail` or `head`, which drops earlier review comments. **On failure:** If `ocr review` exits non-zero (e.g. an LLM connection error), do not retry blindly — consult the Troubleshooting section below for the matching fix before re-running. ### Step 3: Report OCR output includes structured `severity` (critical / high / medium / low) and `category` (bug / security / performance / maintainability / test / style / documentation / other) on each comment. Present results grouped by severity, discarding `low` severity items that are likely false positives or nitpicks. ### Step 4: Fix Before applying fixes, check whether the user requested automatic fixes: - If the user explicitly requested "review and fix" or similar, proceed with automatic fixes - If the user only requested "review" without fix intent, ask for permission before applying any changes When fixing issues and suggestions: - Focus on critical, high, and medium severity items - Apply fixes directly to the code when safe and well-defined - For complex fixes requiring manual intervention, clearly describe what needs to be done - Always verify fixes with the user before committing ## Output Format Each comment in OCR's output contains: - `path`: File path - `content`: Review comment text - `start_line` / `end_line`: Line range (both 0 means positioning failed) - `category`: Issue category (bug, security, performance, maintainability, test, style, documentation, other) - `severity`: Issue severity (critical, high, medium, low) - `suggestion_code`: Optional fix suggestion - `existing_code`: Optional original code snippet - `thinking`: Optional LLM reasoning process Present results grouped by severity using this template: ```markdown ## Code Review Results **Files reviewed**: N **Issues found**: X critical, Y high, Z medium ### Critical - **`path/to/file.java:42`** [bug] — Brief description > Recommendation: How to fix ### High - **`path/to/file.java:26`** [bug] — Brief description > Recommendation: How to fix ### Medium - **`path/to/file.ts:88`** [performance] — Brief description > Recommendation: How to fix (if applicable) ``` If no critical, high, or medium severity issues remain after filtering, state: "Review complete — no critical, high, or medium issues found in N files." **Handling mispositioned comments:** When `start_line` and `end_line` are both `0`, the comment failed to locate the exact position in the file. In such cases: 1. Read the comment content to understand the issue 2. Examine the target file mentioned in the comment 3. Identify the relevant code section based on the comment's context 4. Apply the fix or suggestion to the correct location ## Custom Review Rules If the user wants project-specific rules, OCR resolves them in this priority order: 1. `--rule ` flag (highest) 2. `/.opencodereview/rule.json` 3. `~/.opencodereview/rule.json` 4. Built-in system defaults (lowest) By default, the first matching user rule replaces the built-in system rule. Set `merge_system_rule: true` on a rule entry when the matched system rule and user rule should both be included. Rule file format: ```json { "rules": [ { "path": "**/*.java", "rule": "All new methods must validate required parameters for null", "merge_system_rule": true }, { "path": "**/*mapper*.xml", "rule": "Check SQL for injection risks and missing closing tags" } ] } ``` To preview which rule applies to a file before reviewing: ```bash ocr rules check src/main/java/com/example/Foo.java ``` ## Gotchas - **LLM must be configured first** — `ocr review` will fail loudly if no LLM is reachable. See the Troubleshooting section below if this happens. - **Working directory matters** — `ocr review` operates on the Git repo at the current directory. Use `--repo /path/to/repo` to run from elsewhere. - **Untracked files are reviewed in workspace mode** — running bare `ocr review` includes staged, unstaged, *and* untracked changes. Stage selectively if you want narrower scope. - **Large diffs may hit token limits** — files with very large diffs may be truncated. The default `MAX_TOKENS` is 58888 per request. - **Plan phase triggers at 50 lines** — diffs exceeding 50 changed lines run an extra risk-analysis phase before main review. This adds latency but improves quality. - **Don't pass `--audience human`** — it streams progress UI that pollutes output. Always use `--audience agent`. - **Comment language follows config** — set `language` config to `English` or `Chinese` (default: Chinese) to control review comment language. - **Avoid output truncation** — Large review runs produce verbose output. Never pipe command output to `tail` or `head` as it drops review comments from earlier sections. Use `--output ` and read it in full; on older CLIs, follow the **Output file** guidance above. ## Validation After the review completes, verify success by checking: 1. The command exited with code 0 2. Comments were generated (or "No comments generated" message appears) 3. Warnings (if any) are displayed in stderr If errors occurred, check the stderr warnings for details about which files failed and why. ## Troubleshooting **`ocr: command not found`** Install the CLI: ```bash npm install -g @alibaba-group/open-code-review ``` **`unknown flag: --output`** The CLI is older than v1.10.0. Do not continue the review with plain stdout. Ask the user whether to upgrade (`npm i -g @alibaba-group/open-code-review@latest`) and wait for the answer before proceeding. After the user confirms and the upgrade succeeds, rerun with `--output`. **`ocr review` fails with LLM connection error** Prompt the user to configure an LLM provider. Interactive setup (recommended): ```bash ocr config provider ``` Manual setup (alternative): ```bash ocr config set llm.url https://api.anthropic.com/v1/messages ocr config set llm.auth_token ocr config set llm.model claude-opus-4-6 ocr config set llm.use_anthropic true ``` Verify connectivity with `ocr llm test`. Stop here and ask the user to provide credentials — never invent or hardcode API keys. ## References - Full docs: https://github.com/alibaba/open-code-review - NPM package: https://www.npmjs.com/package/@alibaba-group/open-code-review - Issue tracker: https://github.com/alibaba/open-code-review/issues

相关技能

安全测试

Skill Vetter

人工智能特工的安全第一技能审查。 在安装来自 ClawdHub, GitHub 或其他来源的任何技能之前使用 。 检查红旗,许可范围,可疑图案.

安全测试

Moltguard

MoltGuard——由OpenGuardrails担任OpenClaw保安. 安装 MoltGuard 以保护你和你的人类免受迅速注射、数据过滤和恶意命令的影响。 资料来源:https://github.com/openguardrails/openguardrails/tre…

安全测试

Security Auditor

用于审查安全漏洞代码,实施认证流,审计OWASP Top 10,配置CORS/CSP头,处理秘密,输入验证,SQL注射预防,XSS保护,或任何与安全相关的代码审查.

安全测试

Skill Vetter

安装任何AI代理技能前的安全审查协议. 红旗侦取入证盗取,疏通密码,放出. 风险分类:低/中/高/高。 编制结构化审查报告。 不先运行此功能, 绝不安装不信任的技能 .