rust-code-review

Detect and fix Rust code smells across multi-crate workspaces.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AlexKVal/rust-skills-for-cursor --skill rust-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-code-review
Source: https://github.com/AlexKVal/rust-skills-for-cursor/tree/main/skills/code-review
Command: npx skills add https://github.com/AlexKVal/rust-skills-for-cursor --skill rust-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code smells in Rust slow down delivery, reduce reliability, and increase maintenance burden; this skill analyzes code to detect smells and guides refactoring decisions.

Core Features & Use Cases

  • Automated smell detection across Rust projects (ownership, borrowing, error handling, API design, and structural smells).
  • Auto-fix of high/medium severity issues (where safe) with an accompanying findings report for traceability.
  • Guidance for refactoring decisions (where to move methods, how to reduce boilerplate, and how to enforce better design practices).

Quick Start

Run this skill against your Rust workspace to automatically scan all crates, generate a findings report, apply high/medium fixes, and produce a ready-to-commit change set.

Frequently Asked Questions about rust-code-review

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

FAQPage Schema
How do I find and fix Rust code smells across a multi-crate workspace?

To find and fix Rust code smells across a workspace, scan all crates for ownership, borrowing, and error handling issues to generate a findings report and automatically apply safe repairs.

Can I automate refactoring decisions for Rust API design and structural smells?

Yes, you can automate refactoring guidance for Rust API design by identifying structural smells, reducing boilerplate, and suggesting where to move methods to enforce better design practices.

What is the best way to detect missing must_use and visibility reduction issues in Rust?

Detect missing must_use and visibility reduction issues by running static analysis checks on your Rust codebase, which identifies these common patterns and documents them in a findings report.

Does Rust static analysis work for error handling and ownership smells in multi-crate projects?

Rust static analysis works for multi-crate projects by scanning the entire workspace to detect error handling and ownership smells, then producing traceable progress updates and a ready-to-commit change set.

When should I not use automated refactoring for Rust code quality?

You should not use automated refactoring when low-severity issues require manual intervention, as the automated repair safely targets only high and medium severity Rust code smells.