rust-review

Review Rust code for ownership, lifetimes, unsafe usage, and concurrency issues.

7|Updated Mar 19, 2026

Search Tags:#ownership #concurrency #rust #async #code-review #lifetimes #unsafe

Ready to run

npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill rust-review-camilooscargbaptista

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rust-review
Source: https://github.com/camilooscargbaptista/cto-toolkit/tree/main/rust-review
Command: npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill rust-review-camilooscargbaptista

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies ownership, lifetime, unsafe usage, error-handling, concurrency, and idiomatic issues in Rust code to reduce subtle bugs and runtime failures and to improve maintainability.

Core Features & Use Cases

Reviews Rust source and manifests for unnecessary clones, improper borrowing, and lifetime annotation issues.
Flags unsafe blocks lacking safety rationale, verifies FFI boundaries, and checks Send/Sync implementations.
Audits concurrency and async code for deadlocks, blocking in async contexts, and incorrect task spawning patterns.
Evaluates error handling, panic usage, trait design, macro hygiene, and performance hotspots with practical suggestions.
Use cases: library author safety audit, web service async correctness check, systems code memory-safety review.

Quick Start

Run the rust-review skill against your repository root to produce a prioritized review of ownership, unsafe code, concurrency, and error-handling issues.

Frequently Asked Questions about rust-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I review Rust code for ownership and lifetime issues?▼

Review Rust code for ownership and lifetime issues by analyzing source files and manifests to identify unnecessary clones, improper borrowing, and incorrect lifetime annotations. This reduces subtle memory bugs and improves maintainability across library, web service, and systems projects.

What is the best way to audit unsafe Rust blocks and FFI boundaries?▼

Auditing unsafe Rust blocks involves flagging code that lacks safety rationale and verifying FFI boundaries for correctness. This ensures that unsafe usage is properly justified and that foreign function interfaces maintain memory safety guarantees.

Can I check async Rust code for deadlocks and blocking issues in tokio or actix projects?▼

Yes, you can check async Rust code in tokio, actix, or axum projects. The review audits concurrency patterns to detect deadlocks, blocking operations in async contexts, and incorrect task spawning to ensure runtime correctness.

How do I identify panic and unwrap usage in my Rust web server?▼

Identify panic and unwrap usage in Rust web servers by evaluating error handling patterns across the codebase. The review flags unwrap calls and panic risks, providing practical suggestions for idiomatic error handling improvements.

Does a Rust code review check Send and Sync trait implementations?▼

Yes, a Rust code review checks Send and Sync trait implementations. It verifies incorrect Send and Sync bounds to prevent data races and ensure thread-safe concurrency across async and multi-threaded systems components.