菜单
Review changes. Check that they are correct, consistent with the rest of the specifications, and compliant with the project's conventions. Always load this skill before reviewing changes.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ethereum/consensus-specs --skill review命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Run tests and generate reference tests. All testing goes through `make test`, never `pytest` directly. Always load this skill before running tests.
Write specifications. Always load this skill before writing to `specs`.
Commit changes and open pull requests. Follow the project's conventions for scope, formatting, and writing style. Always load this skill before committing or opening a pull request.
基于 SOC 职业分类
正在显示 SKILL.md
| name | review |
| description | Review changes. Check that they are correct, consistent with the rest of the specifications, and compliant with the project's conventions. Always load this skill before reviewing changes. |
| compatibility | Requires make and uv |
Before reviewing, load the skills that govern the area under review. Their conventions define what a correct change looks like, and a review largely checks the change against them.
Before judging a change, understand what it is meant to accomplish. Consult the pull request description, the linked issue, or the relevant EIP. Correctness is relative to intent, so confirm that the change actually does what it sets out to do before looking for smaller issues.
A change should have a single, well-defined objective. Flag unrelated changes that have been bundled in, and suggest splitting them into separate pull requests. A focused change is easier to review and easier to reason about later.
Terminology must match older specifications. Reuse the existing name for a concept instead of inventing a synonym, so that a term means the same thing across every spec.
The order of sections within a document must match the order established by older specifications. When an item is added or modified, place its section where the equivalent item appears in earlier specs rather than introducing a new arrangement.
The specifications are organized as a sequence of upgrades, where each builds on the one before it. When some change is backported to an older spec so that it is easier to express a change in a newer spec, the functionality in the older spec (if considered stable) must not change unless explicitly stated somewhere.
Only raise an issue when you are confident it is a genuine mistake. Do not report speculative concerns. Stylistic issues are worth reporting, but only when you are confident the code does not adhere to the repository's defined standards.
When suggesting a change, be clear and concise. If necessary, provide an example
so the intent is unambiguous. Keep code suggestions compliant with make lint.
Running the linter over the suggested code, once applied, should produce no
complaints.
