メニュー
Multi-dimensional code review. Use when reviewing PRs, staged changes, or any code diff. Covers scope, dependencies, testing, performance, and security. Based on htmlpage.cn Cursor Code Review methodology.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Anthony Fu's opinionated tooling and conventions for JavaScript/TypeScript projects. Use when setting up new projects, configuring ESLint/Prettier alternatives, monorepos, library publishing, or when the user mentions Anthony Fu's preferences.
Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides.
UnoCSS instant atomic CSS engine, superset of Tailwind CSS. Use when configuring UnoCSS, writing utility rules, shortcuts, or working with presets like Wind, Icons, Attributify.
Apply Beehive Blog v3 coding standards. Use when handwritten code is being designed or edited and you need the repository's layer boundaries, directory responsibilities, config rules, and comment conventions.
Apply the contract-first workflow in Beehive Blog v3. Use when a task changes `v3/api/*.api` or `v3/proto/*.proto` and the contract sequence must be handled correctly.
Guide Beehive Blog v3 implementation work while coding. Use when handwritten business code is being added or changed and you need stage-specific implementation guidance without reloading every project rule.
| name | code-review |
| description | Multi-dimensional code review. Use when reviewing PRs, staged changes, or any code diff. Covers scope, dependencies, testing, performance, and security. Based on htmlpage.cn Cursor Code Review methodology. |
Multi-dimensional code review skill. Use this to systematically review code changes across five dimensions: scope, dependencies, testing, performance, and security. 用于对代码变更进行多维度系统化审查。
| 维度 | 重点问题 | 常见漏项 | 必须深查的场景 |
|---|---|---|---|
| 范围 | 改动是否越界，是否影响非目标模块 | 顺手重构、顺手改命名 | 多文件改动、共享组件 |
| 依赖 | 调用方、配置、路由、状态是否同步更新 | 只改定义不改使用方 | 接口、组件 props、store |
| 测试 | 是否补了单元/集成/冒烟验证 | 只说"建议测试"但不给清单 | 表单、支付、权限、发布 |
| 性能 | 首屏、体积、重复请求、阻塞资源 | 新增库体积、无缓存、重复渲染 | Landing 页、内容页、SSR 页面 |
| 安全 | 输入校验、权限边界、敏感信息泄漏 | 日志泄漏、token 暴露、越权访问 | 登录、用户资料、支付、上传 |
Use this prompt template when asking an AI to review code:
请只审查以下改动范围：
- 文件：<列出改动的文件>
- 目标：<一句话说明这次改动想解决什么>
- 不在范围内：<明确哪些模块不要展开>
请按以下维度输出审查结果：
1. 范围是否越界
2. 依赖与调用方是否漏改
3. 测试与回归项是否不足
4. 性能风险
5. 安全风险
输出要求：
- 只写有根据的问题，不要泛泛而谈
- 每条问题包含：严重级别、位置、原因、建议修复、回归检查点
- 如果没有发现问题，明确说明"未发现高置信问题"，并列出剩余验证风险
Each issue must include:
| Field | Description |
|---|---|
| 严重级别 | 🔴 Critical / 🟠 High / 🟡 Medium / ⚪ Low |
| 位置 | File path and line range |
| 原因 | Why this is a problem |
| 建议修复 | Concrete fix suggestion |
| 回归检查点 | How to verify the fix is correct |