code-review
仓库创建 2026年7月27日最近提交 1 天前SkillHot 收录 1 天前
▸ 精选理由
适合团队规范化评审流程,能快速定位高优先级问题。
这个 Skill 做什么
基于分级清单与 Google 标准对 PR/变更进行代码评审。
按严重性分级的检查清单和 Google 的评审标准来审 PR 或差异,既能找功能 bug,也能抓风格、可维护性和潜在风险。适合在审查 PR、准备自审、回应评审意见或拆分过大的变更时使用。特点是有条理、有优先级,指出问题还能给出可引用的规则或改进建议,方便团队统一质量水准。
▸ 展开 SKILL.md 英文原文
Reviews code changes with a severity-ranked checklist and Google engineering review standards. Use for reviewing PRs, diffs, or staged changes, responding to review feedback, preparing a change for review, or splitting an oversized change.
0
Stars
0
Forks
21
仓库内 Skill
积累中
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/Ludenox-GIT/portable-agent-skills/main/skills/code-review/SKILL.md或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/Ludenox-GIT/portable-agent-skills/main/skills/code-review/SKILL.md"SKILL.MD 节选查看完整文件 ↗
# Code Review ## When to use - Reviewing a PR, diff, patch, or staged/uncommitted changes. - Responding to review feedback on your own change (author side). - Preparing a change for review (self-review pass). - Deciding whether/how to split an oversized change. Do NOT use for: design-doc/RFC review, dedicated security audits (use a security-review skill), CI/branch-protection configuration, or performance reviews of people. ## Core principle (Iron Law) Approve once the change is in a state where it "definitely improves the overall code health of the system being worked on, even if the CL isn't perfect" (Google eng-practices, The Standard of Code Review). There is no perfect code — only
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有