code-review
代码审查技能。用户发送 /review 或要求 review 时触发。 自动检查代码质量、安全问题、架构建议。
Best use case
code-review is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
代码审查技能。用户发送 /review 或要求 review 时触发。 自动检查代码质量、安全问题、架构建议。
Teams using code-review should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/code-review/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How code-review Compares
| Feature / Agent | code-review | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
代码审查技能。用户发送 /review 或要求 review 时触发。 自动检查代码质量、安全问题、架构建议。
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Code Review
## 触发
- `/review` — 审查当前项目的最近改动
- `/review <文件路径>` — 审查指定文件
- "帮我 review"、"代码审查" 等自然语言
## 审查流程
```
1. 确定审查范围（git diff / 指定文件 / 整个项目）
2. 按 checklist 逐项检查
3. 输出审查报告（问题分级：🔴 严重 / 🟡 建议 / 🟢 良好）
```
## Checklist
### 🔴 必须修复
- [ ] 安全漏洞（硬编码密钥、SQL 注入、路径穿越）
- [ ] 明显的 bug（类型错误、空指针、越界）
- [ ] 数据丢失风险（无事务、无备份）
### 🟡 建议改进
- [ ] 代码重复（DRY 违反）
- [ ] 函数过长（>50 行考虑拆分）
- [ ] 命名不清晰
- [ ] 缺少错误处理
- [ ] 缺少类型注解（Python）
- [ ] 缺少 docstring
### 🟢 架构层面
- [ ] 模块职责是否单一
- [ ] 接口设计是否清晰
- [ ] 依赖方向是否合理
- [ ] 是否有循环依赖
## 输出格式
```
## 审查报告: {文件/项目名}
### 🔴 严重问题 (N 个)
1. **[文件:行号]** 问题描述
建议修复方案
### 🟡 改进建议 (N 个)
1. **[文件:行号]** 建议描述
### 🟢 总体评价
一句话总结代码质量和架构状态
```
## 快速命令
```bash
# 审查最近 commit 的改动
git diff HEAD~1 --stat
git diff HEAD~1 -- <有改动的文件>
# 审查未提交的改动
git diff --stat
git diff -- <文件>
# 检查 Python 代码质量
python3 -m py_compile <文件>
python3 -m pytest --tb=short
```Related Skills
Maintenance Skill
飞书多 Agent 项目维护指南 - 仅供维护 feishu-multi-agent 项目时使用。
feishu-doc-writer
Feishu document writing skill. Handles known API pitfalls (block ordering, unsupported formats). Activate when writing content into Feishu docs or creating structured documents.
feishu-chat
飞书群聊管理：创建群、添加/移除成员、修改群信息。需要 exec 权限执行 curl 命令。
delegate-agent
Delegate tasks to agents asynchronously. Triggers on "让XX做", "delegate to", "assign to", "派发", "布置任务".
Config Update Skill
OpenClaw 配置安全更新指南。
agent-comm
跨 Agent 通信。当用户说"问XX"、"让XX做"、"发给XX"、"check agent status"时使用。
project-switcher
多项目管理和目录切换。用户发送 /repo 时列出项目，选择后切换工作目录。 适用于 coder agent 同时维护多个代码仓库的场景。
git-workflow
Git 工作流规范。管理分支、commit、PR 的标准流程。 用户发送 /git 或涉及版本控制操作时触发。
feishu-multi-agent
飞书多 Agent 系统搭建指南。当用户要求创建新的功能 Agent、配置飞书群聊绑定、 搭建多 Agent 协作系统时激活此 skill。 触发词：创建 agent、新建 agent、添加 agent、create agent、多 agent、飞书绑定。
flutter-dart-code-review
库无关的Flutter/Dart代码审查清单，涵盖Widget最佳实践、状态管理模式（BLoC、Riverpod、Provider、GetX、MobX、Signals）、Dart惯用法、性能、可访问性、安全性和整洁架构。
security-review
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
addressing-pr-review-comments
Address all valid review comments on a PR for the current branch in the streamlit/streamlit repo. Covers both inline review comments and general PR (issue) comments. Use when a PR has reviewer feedback to address, including code changes, style fixes, and documentation updates.