// Review Rust code for correctness, design principles, and rule compliance.
Use when designing error types, wrapping third-party errors, seeing repeated map_err calls with same error types, building modular error hierarchies with thiserror, choosing between custom errors vs anyhow::Result, or writing Result-returning functions in Rust.
Search and evaluate Rust crates for a problem. Presents options for user approval.
When and what to test in Rust. Types handle compile-time invariants; tests verify runtime behavior types cannot express.
Use when writing Rust structs with generic type parameters, implementing traits for polymorphism, designing service/client/handler layers, choosing between Box<dyn Trait> vs enum vs generics, adding middleware (retry, logging, caching), wrapping or decorating existing types, forwarding methods to inner fields, or refactoring to reduce duplication across similar structs.
Helper skill for searching Rust documentation. Use when agents need to find crate docs, API usage, trait implementations, or examples from local and online sources.
| name | rs-review |
| description | Review Rust code for correctness, design principles, and rule compliance. |
| user-invocable | true |
| context | fork |
| allowed-tools | ["Read","Grep","Glob","Bash","Task"] |
| agent | rust-code-reviewer |
Review Rust code for rule compliance and best practices.
/rs-review # Review all modified .rs files
/rs-review src/lib.rs # Review specific file
/rs-review src/ # Review directory
P0 - Critical:
P1 - Important:
Smells:
map_err → delegates to rust-error-handling-checkerrust-abstraction-builderrust-compile-challenger## Review: [filename]
### Critical (must fix)
- [ ] Issue → fix
### Warning (should fix)
- [ ] Issue → fix
### Suggestion
- [ ] Issue → fix
For fast checks without deep analysis:
/rs-review --quick # clippy + fmt only