使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/tyelf22/free-skills --skill code-review-companion开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Code Review Companion
Paste in a diff and get a structured review: bugs, edge cases, naming, and the one thing worth fixing before merge.
{{input}} in the steps below is the user's input (Paste a diff or code snippet).
Steps
1. Scan for bugs
Read {{input}} line by line and flag anything that looks like a bug: logic errors, typos, off-by-ones, wrong comparisons. Quote the line.
2. Check edge cases
Identify unhandled inputs: null/undefined, empty collections, zero, negatives, unexpected types. List what's missing.
3. Review naming and clarity
Flag names, structures, or conditions that would confuse the next reader. Suggest a clearer alternative for each.
4. Pick the one fix that matters
Name the single issue that should block merging and explain its impact in one sentence.
Example
Paste a diff or code snippet: function getDiscount(user) { if (user.role = 'admin') return 1; return user.tier === 'gold' ? 0.2 : 0; }
Output:
CODE REVIEW
BUGS
• Line 2 uses `=` (assignment) not `===` — always sets role to 'admin' and returns true.
EDGE CASES
• No handling for missing `user.tier` — falls through to 0, which may be fine but isn't explicit.
NAMING
• `getDiscount` returning 1 (100%) for admins is surprising — consider `getDiscountRate` or a comment.
FIX FIRST
The `=` vs `===` bug — it grants every user an admin-level discount.
