- name
SKILL.md
技能文件保留在发布者的仓库中。
在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add MiniMax-AI/mcode-stack --skill engineering-code-review -a cursor -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add MiniMax-AI/mcode-stack --skill engineering-code-review -a claude-code -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add MiniMax-AI/mcode-stack --skill engineering-code-review -a codex -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add MiniMax-AI/mcode-stack --skill engineering-code-review -a grok -y在 Grok Bot 聊天中发送复制的消息。Bot 会从 GitHub 获取这个 SKILL.md,并添加到你所有 Bot 共享的技能中。
Install this skill: https://github.com/MiniMax-AI/mcode-stack/tree/HEAD/stacks/ronny/skills/engineering-code-review来自发布者
Use code review to protect and improve long-term code health while still allowing useful changes to land. The standard is not perfection; the standard is that the change improves the system overall and does not introduce unacceptable risk.
Adapted from Google Engineering Practices Documentation, especially the code review overview, reviewer guide, standard of review, navigation, speed, small changes, and emergency guidance. Sources: https://google.github.io/eng-practices/, https://google.github.io/eng-practices/review/reviewer/standard.html, https://google.github.io/eng-practices/review/reviewer/navigate.html, https://google.github.io/eng-practices/review/reviewer/speed.html, https://google.github.io/eng-practices/review/developer/small-cls.html, and https://google.github.io/eng-practices/review/emergencies.html. License: CC-BY 3.0.
Establish scope.
Gather review material.
git status --short, the target branch or base SHA when known, and the local diff.Take the broad view first.
Review the main design before details.
Review every human-written line in your assigned scope.
Check the change against the review checklist below.
Check verification evidence.
Make a verdict.
APPROVE: code health improves and remaining comments are non-blocking.APPROVE_WITH_COMMENTS: remaining comments are minor, optional, or the author can be trusted to handle them without another review round.REQUEST_CHANGES: correctness, design, maintainability, test, documentation, or risk issues remain.NEEDS_SPECIALIST: another reviewer must cover a domain you cannot responsibly assess.Escalate to a specialist when you cannot confidently assess security, privacy, accessibility, internationalization, concurrency, infrastructure, data migration, or domain-specific correctness.
BLOCKER: must be fixed before approval.IMPORTANT: should be fixed before approval unless there is a written rationale.QUESTION: answer needed before final verdict.NIT: polish that must not block approval.OPTIONAL: suggestion the author may decline.FYI: learning or future consideration, not a requested change.Lead with findings, highest severity first. Use file and line references when available.
## Findings
- [BLOCKER] path/file.ext:123 - Problem. Why it matters. Required change.
- [IMPORTANT] path/file.ext:45 - Problem. Why it matters. Suggested fix.
## Open Questions
- ...
## Verdict
REQUEST_CHANGES | APPROVE_WITH_COMMENTS | APPROVE | NEEDS_SPECIALIST
## Notes
- Scope reviewed:
- Tests/commands checked:
- Follow-ups:
If no issues are found, say that clearly and still mention any unverified scope or residual risk.
Also published in agentara/skills (MIT, Copyright (c) 2026 agentara) by the same author. The content is adapted from Google Engineering Practices under CC-BY 3.0; see the source note above. Full notices: NOTICE.md.
Use when reviewing code, pull requests, patches, CLs, diffs, or proposed implementations for engineering quality, code health, design, functionality, tests, maintainability, specialist risk, or approv
---name: engineering-code-reviewdescription: Use when reviewing code, pull requests, patches, CLs, diffs, or proposed implementations for engineering…---# stacks/ronny/skills/engineering-code-review/SKILL.md概览
Use when reviewing code, pull requests, patches, CLs, diffs, or proposed implementations for engineering quality, code health, design, functionality, tests, maintainability, specialist risk, or approval risk. TRIGGER on "review this PR", "code review", "LGTM?", "approve?", "is this code/diff/change safe to merge/deploy?", and local diff reviews. DO NOT TRIGGER for PR descriptions, PR splitting, author review-feedback responses, or non-code safety questions unless code review is requested.
常见问题
从发布者处下载 stacks/ronny/skills/engineering-code-review/SKILL.md,或复制路径后打开仓库。PlugMCP 只收录该技能,不托管文件。
发布者将它存放在 https://github.com/MiniMax-AI/mcode-stack。
Claude、Cursor、Codex 和 Grok Build 可以读取你从发布者仓库添加的 SKILL.md。在聊天中发送技能的 GitHub 文件夹链接,Grok Bot 就会安装它。