Can it help find performance bottlenecks in async code?

Yes, it specifically scans for 'sync' primitives that block the async executor, such as std::sync::Mutex, and recommends tokio-based alternatives.

Does it support the Tower middleware ecosystem?

Yes, it identifies and recommends common Tower layers like TraceLayer, TimeoutLayer, and CorsLayer to improve observability and reliability.

Which Rust web frameworks are supported?

This skill is specifically optimized for projects using Axum (0.7+), Actix-web, and Rocket.

Does it review API security patterns?

It reviews extractor validation, middleware implementation for auth, and ensures that internal error details aren't leaked in HTTP responses.

How does it handle route organization?

It checks for route nesting and resource grouping, recommending Router::nest patterns for Axum to prevent main.rs files from becoming unmanageable.

Rust API Reviewer

Name: Rust API Reviewer
Author: physics91

byphysics91

API Development

Reviews and optimizes Rust-based web APIs built with Axum, Actix-web, and Rocket frameworks to ensure performant async patterns.

About

The Rust API Reviewer skill is a specialized auditing tool for backend developers working with the Rust web ecosystem. It analyzes project structures to enforce best practices across routing organization, state management, and middleware implementation. By detecting critical anti-patterns—such as using blocking Mutexes in async contexts or manual JSON parsing—it helps developers build safer, more scalable RESTful services while providing framework-specific recommendations for Axum, Actix-web, and Rocket.

Key Features

Validation of extractor ordering and type-safe payload handling
Detection of performance-blocking patterns like std::sync::Mutex usage
0 GitHub stars
Deep analysis of async handler patterns and state management
Automated framework detection for Axum, Actix-web, and Rocket
Review of Tower middleware stacks and error response implementations

Use Cases

Optimizing async performance by replacing blocking synchronization primitives
Refactoring monolithic route files into modular, nested routers
Standardizing API error handling with custom IntoResponse implementations

About

Key Features

Validation of extractor ordering and type-safe payload handling
Detection of performance-blocking patterns like std::sync::Mutex usage
0 GitHub stars
Deep analysis of async handler patterns and state management
Automated framework detection for Axum, Actix-web, and Rocket
Review of Tower middleware stacks and error response implementations

Use Cases

Optimizing async performance by replacing blocking synchronization primitives
Refactoring monolithic route files into modular, nested routers
Standardizing API error handling with custom IntoResponse implementations