القائمة
[DRAFT] 第 1 轮 Rust 工程化审查。对一个迁移单元或已收批的 review batch 检查 Rust 模块结构、可见性、所有权、lint 和可维护性；默认审查不改生产代码，修复需单独实现并重跑 R0。
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review one mvsep-rs rewrite batch quality gate without writing production code. Use when the user asks for behavior parity review, error tracing review, async or ergonomics review, data structure or algorithm review, Rust style audit, frontend UX audit, or promotion readiness for a mvsep-rs migration batch.
Expand dependency sources and align canonical shared capabilities, Rust crate reuse, adapters, hand-written Burn gaps, fixtures, and bootstrap records for Vocal2Midi. Use before implementation when imports, native/FFI sources, dependency mismatch, shared model prerequisites, temporary dependency copies, Cargo coordination, or manifest re-cut decisions affect a unit.
Review one Vocal2Midi Rust migration unit quality gate without writing production code. Use for Python/Rust behavior parity, dependency/seam, error tracing, data/algorithm, Rust style, architecture, ergonomics, or promotion readiness.
Coordinate the Vocal2Midi Python-to-Rust rewrite. Use when the user asks to continue, plan, route, re-cut, shard, implement, audit, promote, choose serial or coordinated-parallel execution, or select the next migration unit; when shared Burn gaps, dependency source expansion, capability coverage, or workflow may change the manifest inventory.
Implement exactly one confirmed Vocal2Midi Rust migration unit as the writer role. Use when dependency discovery has accepted the boundary, canonical dependencies, and legacy public behavior seam, and the user asks to add fixtures, port behavior, or prepare one unit for review. Do not use for review-only or shared dependency coordination requests.
[DRAFT] 消费 crate reconnaissance 或用户手动生态证据，按 NOTES.md 中的偏好对齐 Python/Rust 或 legacy/Rust 依赖。覆盖 canonical shared dependencies、crate/backend/adapter/手写能力组合、manifest 重切、seam、验证和桥接；用于避免串行或并行 writer 创建冲突依赖副本。
| name | py2rs-review-r1-rust-style |
| description | [DRAFT] 第 1 轮 Rust 工程化审查。对一个迁移单元或已收批的 review batch 检查 Rust 模块结构、可见性、所有权、lint 和可维护性；默认审查不改生产代码，修复需单独实现并重跑 R0。 |
R1 检查 Rust 代码是否从“行为等价但直译”走向可维护的 Rust。它不重新定义项目架构 seam。
pass or accepted pass-with-followups.reimplemented.pub surface is minimal and matches the project seam.&str, &[T] or borrowed data where that fits the seam.unwrap/expect without explicit justification.cargo fmt, cargo clippy or project lint policy are considered.pass, pass-with-followups or fail for each in-scope unit.Default review-gate mode does not edit production code. If the user explicitly asks this skill to fix issues:
Use project convention or:
reviews/YYYY-MM-DD-<unit-or-batch-id>-rust-style.md
Include:
not_required only when the manifest
does not require R1 for that unit)