원클릭으로 Manus에서 모든 스킬 실행

시작하기

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 저장소 열기 Creator 저장소 보기

다운로드

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