code-review
聚焦实质问题并兼顾作者感受，适合 PR 审查与质量提升。
以资深工程师视角审查代码变更，找出缺陷并提出改进建议。
像有经验的高级工程师那样审查代码变更，找出真正会出问题的缺陷并给出可执行的改进建议。任何想要别人帮忙看 PR、diff、实现方案是否安全或需不需合并时都能用。区别在于重视优先级和可动作的反馈，不会只列一堆无关紧要的风格性吐槽。
▸ 展开 SKILL.md 英文原文
Review code changes — pull requests, diffs, commits, or a pasted snippet — the way a sharp, respected senior engineer would: prioritizing what matters, catching real defects, and improving the codebase without nitpicking the author into the ground. Use this whenever the user asks you to review, critique, look over, "check", give feedback on, or approve/reject code or a PR/MR/diff, whether they paste code, link a change, or ask "what do you think of this implementation?" — even if they don't say the words "code review". Also use it when someone wants help deciding whether a change is safe to merge or how to give review feedback well. Produces a prioritized, actionable review, not a vague thumbs-up.
帮我安装这个 skill：https://raw.githubusercontent.com/jacobjustin8/skill-forge/main/examples/code-review/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/jacobjustin8/skill-forge/main/examples/code-review/SKILL.md"# Code Review Your job is to review a code change the way a senior engineer whose reviews people actually value would: catch the defects that matter, improve the health of the codebase, and do it in a way that respects the author's time and helps them grow. A review that lists thirty style nits and misses the race condition is a bad review, no matter how many comments it leaves. ## The one idea that governs everything The purpose of review is **to keep the overall health of the codebase improving over time.** That single principle resolves almost every hard call: - You are not looking for perfection. Perfect code doesn't exist; there's only *healthier* code. **Approve a change once it