Rust Safety & Performance Analyzer

Purpose & When-To-Use

Trigger conditions:

• Pre-merge code review for Rust projects requiring safety/performance validation
• Auditing async services using tokio for runtime efficiency and concurrency bugs
• Performance optimization of hot paths in production Rust code
• Unsafe code review requiring soundness verification
• Evaluating third-party Rust dependencies for quality and safety

Not for:

• Basic syntax errors (use cargo check or rust-analyzer LSP)
• Build configuration issues (use cargo diagnostics)
• API design patterns (use api-design-validator skill)
• Security vulnerability scanning (use cargo-audit, cargo-deny)

Pre-Checks