菜单
Use Alibaba Open Code Review (`ocr`) to review git diffs, staged changes, branches, or scan a workspace, then summarize findings and optionally fix high-confidence issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guide for building custom interactive web apps ("mini apps") displayed in browser tabs — scaffolding, iframe constraints, bidirectional messaging with the sandbox, and iteration workflows.
Review a change against release gates, rollback safety, validation evidence, and operational risk.
Complete guide for the Figma plugin — REST API access, real-time selection monitoring via CDP, and the figma-app interactive UI. Read this IMMEDIATELY when the user asks to work with Figma.
Complete guide for the GitHub plugin — REST API access for repositories, issues, pull requests, actions, releases, and search using a GitHub Personal Access Token.
Best practices for using the clodex built-in JavaScript sandbox. Explains how to access APIs for browser debugging/interaction, use external dependencies, file system access, running mini-apps, etc.
Use OpenManus as an external autonomous Python agent for long-running research, browser-style exploration, data analysis, or multi-step execution tasks from inside a mounted workspace.
| name | open-code-review |
| description | Use Alibaba Open Code Review (`ocr`) to review git diffs, staged changes, branches, or scan a workspace, then summarize findings and optionally fix high-confidence issues. |
Use this skill when the user asks for an AI code review, PR review, security review, bug-risk review, regression check, or asks to run alibaba/open-code-review.
This plugin integrates Alibaba Open Code Review through its local CLI command ocr. It should run inside the mounted workspace, never against unrelated directories.
First check whether the CLI exists:
ocr --version
If ocr is missing, tell the user to install Alibaba Open Code Review from https://github.com/alibaba/open-code-review and stop. Do not fabricate review results.
Prefer the narrowest review that matches the request:
# Review current working-tree changes.
ocr review
# Review staged changes only.
ocr review --staged
# Review changes against a base branch.
ocr review --base main
# Machine-readable output for agent post-processing.
ocr review --format json --audience agent
# Broader workspace scan when the user asks for a full audit.
ocr scan --format json --audience agent
If the repository's default branch is not obvious, inspect git first:
git rev-parse --show-toplevel
git branch --show-current
git remote show origin
git status --short and, when useful, git diff --stat.ocr review --format json --audience agent for changed files, or ocr scan --format json --audience agent for an explicit full audit.Lead with actionable findings. Keep summaries short.
Use this shape:
Found N issue(s).
- [High] path/to/file.ts:42 — Issue title.
Impact: ...
Fix: ...
No high-confidence issues found.
When no issues are found, say that clearly and mention the reviewed scope.
w48b2/; use project-relative paths.