rs-reviewer

Reviewing Rust code for ownership involves evaluating borrowing, lifetimes, and data movement against idiomatic patterns across crates and modules to ensure safe memory management without unnecessary clones.

Checking unsafe Rust blocks involves detecting each block and ensuring proper safety documentation and invariants are clearly stated to maintain memory safety guarantees across FFI boundaries and asynchronous components.

Assessing error handling across Rust crates involves evaluating error propagation and ensuring clear error context and well-structured architecture with documented decisions across library APIs and async boundaries.

Yes, you can review Rust code for FFI boundaries and asynchronous components by applying pattern analysis to detect unsafe usage and ensure architectural patterns maintain safety and reliability across module interfaces.

You need to review Rust code for idiomatic architecture patterns when developing library APIs, CLI tools, or embedded projects to improve safety, enforce coding practices, and ensure well-structured architectural decisions.