菜单
Perform findings-first Rust review with emphasis on correctness, safety, concurrency risk, and contract stability. Use when reviewing Rust changes before merge or release, validating an implementer's work, or producing actionable review findings instead of a summary-first response.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guide Rust implementation work with an explicit checklist for correctness, maintainability, and verification evidence. Use when writing, changing, or extending Rust code; implementing a bug fix or feature; or driving a disciplined builder role in a Rust workflow.
Validate Rust evidence and quality gates before merge or release decisions. Use when implementation and review are complete, when a maintainer needs an approve or hold decision, or when checking the required evidence set such as cargo fmt, clippy, test, and audit.
| name | rust-reviewer |
| description | Perform findings-first Rust review with emphasis on correctness, safety, concurrency risk, and contract stability. Use when reviewing Rust changes before merge or release, validating an implementer's work, or producing actionable review findings instead of a summary-first response. |
Perform findings-first Rust review with emphasis on correctness, safety, and contract stability.
Use this skill when reviewing Rust changes before merge, before release, or before handing work back to an implementer.
unsafe invariantsPresent findings before summary. Each finding should include:
If no findings are present, say so explicitly and note any remaining test or evidence gaps.
cargo-audit when dependency risk is part of the review surfaceunsafe paths were touched