code-review
starsforks
How to install code-review?
lightpointventures/claude-code-starter/code-review
$npx -y skills add lightpointventures/claude-code-starter --skill code-review当用户想审查代码、检查代码质量、提交前 review、找 bug 时使用 — 从安全性、可读性、潜在 bug 三个维度审查代码
SKILL.md
| 1 | # 代码审查 |
| 2 | |
| 3 | 审查当前未提交的代码更改，帮用户在提交前发现问题。 |
| 4 | |
| 5 | ## 步骤 |
| 6 | |
| 7 | ### 1. 获取更改内容 |
| 8 | |
| 9 | 运行 `git diff` 和 `git diff --staged` 获取所有未提交的更改。 |
| 10 | |
| 11 | 如果没有任何更改，告诉用户「没有需要审查的代码更改」并结束。 |
| 12 | |
| 13 | ### 2. 逐文件审查 |
| 14 | |
| 15 | 对每个改动的文件，从以下三个维度检查： |
| 16 | |
| 17 | **安全性** |
| 18 | - 是否有硬编码的密钥、密码、token |
| 19 | - 是否有 SQL 注入、XSS 等安全漏洞 |
| 20 | - 是否有不安全的文件操作或命令执行 |
| 21 | - 用户输入是否经过验证 |
| 22 | |
| 23 | **可读性** |
| 24 | - 变量和函数命名是否清晰 |
| 25 | - 逻辑是否容易理解 |
| 26 | - 是否有过于复杂的嵌套或过长的函数 |
| 27 | - 是否与项目现有风格一致 |
| 28 | |
| 29 | **潜在 Bug** |
| 30 | - 边界条件是否处理（空值、空列表、超出范围） |
| 31 | - 错误处理是否完整（try/catch 是否合理） |
| 32 | - 是否有逻辑错误（条件判断、循环终止条件） |
| 33 | - 是否可能影响现有功能 |
| 34 | |
| 35 | ### 3. 输出审查报告 |
| 36 | |
| 37 | 用中文输出简洁的审查报告，格式如下： |
| 38 | |
| 39 | ``` |
| 40 | ## 审查结果 |
| 41 | |
| 42 | ### 需要修复 |
| 43 | - [文件名:行号] 问题描述 + 建议的修复方式 |
| 44 | |
| 45 | ### 建议改进 |
| 46 | - [文件名:行号] 改进描述 |
| 47 | |
| 48 | ### 没问题 |
| 49 | - 列出审查通过的文件 |
| 50 | ``` |
| 51 | |
| 52 | 规则： |
| 53 | - 只报告真正有价值的问题，不要吹毛求疵 |
| 54 | - 每个问题给出具体的修复建议，不要只说「这里有问题」 |
| 55 | - 如果代码没有问题，直接说「代码看起来没问题，可以提交」 |
| 56 | - 不要建议添加注释、文档或与改动无关的重构 |
People who liked this also viewed
6 picksType
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026
- code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026
- baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 2026
- code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 2026
- code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 2026
