review-rust

Coordinates specialized Rust sub-agents to audit async and database code with cargo/clippy checks.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/arthrod/conejo-skills --skill review-rust
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-rust
Source: https://github.com/arthrod/conejo-skills/tree/main/skills/review-rust
Command: npx skills add https://github.com/arthrod/conejo-skills --skill review-rust

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the complexity of modern Rust development by providing a systematic, multi-agent review process that ensures code quality, safety, and adherence to the latest language standards.

Core Features & Use Cases

  • Automated Linting & Verification: Integrates clippy and cargo checks to catch performance and safety issues before human review.
  • Edition 2024 Awareness: Specifically calibrated to enforce new Rust 2024 edition requirements, including unsafe block handling and lifetime capture rules.
  • Technology-Specific Audits: Automatically detects and dispatches specialized sub-agents for Tokio, Axum, SQLx, Serde, and FFI-heavy codebases.

Quick Start

Run the review-rust skill on the current directory to perform a comprehensive audit of all modified Rust files.

Frequently Asked Questions about review-rust

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

FAQPage Schema
How do I perform a comprehensive Rust code review for async runtimes and database layers?

Yes, Rust code review can automatically detect and audit Tokio, Axum, SQLx, Serde, and FFI-heavy codebases. It dispatches specialized sub-agents to apply technology-specific verification protocols for each framework.

Does this Rust code review process enforce Rust Edition 2024 standards?

Yes, the Rust code review process is calibrated to enforce Rust Edition 2024 requirements. It specifically checks for proper unsafe block handling and correct lifetime capture rules across all modified files.

What is the best way to automate linting and safety checks for a Rust pull request?

To start a Rust code audit, run the review skill on your current directory to analyze all modified Rust files. The process automatically coordinates specialized sub-agents to execute clippy, cargo checks, and safety invariant verification.

When do I need a specialized Rust audit for unsafe code and ownership invariants?

You need a specialized Rust audit when modifying code with unsafe blocks, complex async ownership, or FFI boundaries. It ensures strict adherence to MSRV, modern edition standards, and sound error handling protocols.