菜单
Enforces Rust development policies including zero warnings, static dispatch preference, minimal Arc usage, and comprehensive testing requirements. Use when reviewing Rust code, writing new Rust code, or checking compliance with project policies.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | policy-rust |
| description | Enforces Rust development policies including zero warnings, static dispatch preference, minimal Arc usage, and comprehensive testing requirements. Use when reviewing Rust code, writing new Rust code, or checking compliance with project policies. |
| metadata | {"author":"aiassisted","version":"1.0"} |
Enforces core Rust development policies for the aiassisted project. Use this skill to verify code compliance or guide implementation.
Use this skill when:
| Policy | Requirement |
|---|---|
| Zero warnings | cargo check must produce 0 warnings |
| Static dispatch | Prefer generics over dyn traits |
| Minimal Arc | Use Arc only for actual concurrent sharing |
| Testing | Unit tests for all modules (positive + negative) |
| Integration tests | Workflow tests in tests/ directory |
Verify no warnings:
cargo check 2>&1 | grep -c warning # Must be 0
Common fixes:
_ or remove#[allow(dead_code)]Check for dynamic dispatch patterns:
// ❌ Avoid
fn process(handler: &dyn Handler) { }
fn process(handler: Box<dyn Handler>) { }
// ✅ Prefer
fn process<H: Handler>(handler: &H) { }
fn process(handler: impl Handler) { }
Acceptable exceptions:
Review Arc usage - this CLI runs sequentially with no shared state:
// ❌ Avoid in this codebase
fn execute(fs: Arc<dyn FileSystem>) { }
// ✅ Prefer
fn execute<F: FileSystem>(fs: &F) { }
Arc is acceptable for:
Every module must have:
#[cfg(test)]
mod tests {
use super::*;
#[test]
fn test_function_success() { } // Positive test
#[test]
fn test_function_error() { } // Negative test
#[test]
fn test_function_edge_case() { } // Edge case
}
Required coverage:
Mock dependencies with mockall:
use mockall::{mock, predicate::*};
mock! {
pub FileSystem {}
impl crate::core::infra::FileSystem for FileSystem {
async fn read(&self, path: &Path) -> Result<String>;
}
}
Located in tests/ directory, use real implementations:
use wiremock::{Mock, MockServer, ResponseTemplate};
#[tokio::test]
async fn test_full_workflow() {
let mock_server = MockServer::start().await;
// Test with real HTTP client
}
Check warnings:
cargo check 2>&1 | grep warning
Search for dyn usage:
grep -r "dyn " src/
Search for Arc usage:
grep -r "Arc<" src/
Verify test coverage:
cargo test
Check for missing tests:
Look for modules without #[cfg(test)]
For comprehensive policy documentation, see rust-policy-guide.md.
Generates commit messages following Conventional Commits 1.0.0 specification. Use when the user asks to commit changes, write commit messages, or when staging and committing code changes.
Initialize and configure multi-project memory bank structure. Use when the user asks to set up a memory bank, initialize project context, or create the .memory-bank directory.
Creates and reviews documentation embedded in source code including doc comments, API documentation, and inline documentation. Use when writing code documentation, reviewing doc quality, or adding examples to code.
Creates and manages project-level documentation including READMEs, tutorials, how-to guides, and architectural docs. Use when creating user-facing documentation, writing tutorials, or organizing project documentation following Diataxis framework.
Review code changes for quality, design, and maintainability. Use when reviewing pull requests, code changes, or performing code reviews. Applies general engineering code review standards.
Review Rust code changes for safety, idioms, and patterns. Use when reviewing Rust code, checking ownership and lifetimes, unsafe blocks, error handling, or Rust-specific patterns like builders and typestate.