一键在 Manus 中运行任何 Skill

开始使用

pluto-review

星标7

分支3

更新时间2026年6月8日 08:20

Pluto-specific code review guidelines. Use as a general guideline when asked to conduct a code review.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

NethermindEth

NethermindEth/pluto

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

相关职业SOC

基于 SOC 职业分类

软件质量保证分析师与测试员计算机与数学类职业·SOC 15-1253

文件资源管理器

2 个文件

SKILL.md

readonly

name	pluto-review
description	Pluto-specific code review guidelines. Use as a general guideline when asked to conduct a code review.

Principles:

Functional equivalence first; document and justify deviations.
Use Charon v1.7.1 as the Go parity baseline. For DKG, sync, reshare, FetchDefinition, and peer-indexed broadcast code, load references/trail-of-bits-charon-v2-audit.md and apply it as a required security overlay when v1.7.1 behavior conflicts with the audit.
Evidence-based: prefer tests, outputs, and file/line references over guesses.
Minimal change bias; avoid scope creep.
No time estimates in review output.

When producing a review, include:

Summary (1–3 sentences)
Findings (ordered by severity)
Parity matrix (if applicable)
Tests (run or not run)
Open questions/assumptions

Severity model:

Critical: breaks contract, security issue, incompatible output/protocol.
High: user-visible regression or parity gap with operational impact.
Medium: behavioral difference with limited impact or edge cases.
Low: minor inconsistency or optional improvement.

Findings format (use path:line references, 1-based):

- [Severity] Title
  Impact: ...
  Evidence: pluto/crates/foo/src/lib.rs:123
  Go reference: charon/cmd/foo.go:456
  Recommendation: ...

Parity matrix template:

Component	Go	Rust	Match	Notes
CLI flag --foo	present	present	yes
Error string for missing key	"..."	"..."	no	mismatch in punctuation
Wire format	pbio	pbio	yes

同仓库更多 Skills

同仓库

rust-style

NethermindEth/pluto

General Rust conventions for Pluto. Use it once for understanding the codebase better.

2026-06-167

charon-guide

NethermindEth/pluto

Use when porting Charon components to understand Go codebase architecture, workflow, design patterns, or component responsibilities

2026-06-087

porting

NethermindEth/pluto

Guides Go→Rust porting for Pluto. Invoke when asked to port, implement parity for, or translate a Go component.

2026-06-087

review-pr

NethermindEth/pluto

Full multi-agent code review for a Pluto PR. Spawns parallel agents covering functional correctness, security, Rust style, and code quality, then posts all findings as isolated GitHub review comments and submits a final approve/request-changes verdict. Invoke as `/review-pr <PR-number>` or `/review-pr <GitHub-PR-URL>`.

2026-06-087

loop-review-pr

NethermindEth/pluto

Iteratively review and fix a Pluto PR until it is "ideal" — drives the /review-pr multi-agent pipeline inside /ralph-loop, applying fixes between iterations and never posting inline comments. After the loop terminates, posts a single summary comment to the GitHub PR with everything that was resolved. Invoke as `/loop-review-pr <PR-number|PR-URL> [--max-iterations N]`.

2026-05-187

rust-p2p

NethermindEth/pluto

Use when implementing, reviewing, debugging, or explaining Pluto Rust libp2p code: Node/P2PContext ownership, PlutoBehaviour composition, NetworkBehaviour and ConnectionHandler protocols, relay/force-direct/quic-upgrade behaviours, peerinfo/parsigex protocol handlers, DKG protocol handlers, and P2P tests.

2026-04-297

name	pluto-review
description	Pluto-specific code review guidelines. Use as a general guideline when asked to conduct a code review.

Principles:

Functional equivalence first; document and justify deviations.
Use Charon v1.7.1 as the Go parity baseline. For DKG, sync, reshare, FetchDefinition, and peer-indexed broadcast code, load references/trail-of-bits-charon-v2-audit.md and apply it as a required security overlay when v1.7.1 behavior conflicts with the audit.
Evidence-based: prefer tests, outputs, and file/line references over guesses.
Minimal change bias; avoid scope creep.
No time estimates in review output.

When producing a review, include:

Summary (1–3 sentences)
Findings (ordered by severity)
Parity matrix (if applicable)
Tests (run or not run)
Open questions/assumptions

Severity model:

Critical: breaks contract, security issue, incompatible output/protocol.
High: user-visible regression or parity gap with operational impact.
Medium: behavioral difference with limited impact or edge cases.
Low: minor inconsistency or optional improvement.

Findings format (use path:line references, 1-based):

- [Severity] Title
  Impact: ...
  Evidence: pluto/crates/foo/src/lib.rs:123
  Go reference: charon/cmd/foo.go:456
  Recommendation: ...

Parity matrix template:

Component	Go	Rust	Match	Notes
CLI flag --foo	present	present	yes
Error string for missing key	"..."	"..."	no	mismatch in punctuation
Wire format	pbio	pbio	yes