Skill Detail

Review Rust code with rule-cited findings using BeautifulRust

Review a Rust file, crate or diff with scoped tool checks and prioritized findings that cite source rules, locations and concrete fixes.

Code Quality & ReviewMulti-Framework
Code Quality & Review Multi-Framework Published
⭐ 1.3k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill review-rust-code-with-rule-cited-findings-using-beautifulrust Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Agent Skills-compatible coding agent; Git for manual installation; Rust toolchain and Cargo for optional mechanical checks
Install & setup
Clone the upstream repository and select the inspected revision: git clone https://github.com/morganlinton/BeautifulRust.git cd BeautifulRust git checkout –detach 58757ee890da9b3c8d5b785adc7a8d53cce27307 Install the complete rust-best-practices, rust-review and rust-port folders, including references, into your agent's supported skills directory following the pinned README. For a runtime using the shared user skills directory: mkdir -p ~/.agents/skills cp -R skills/rust-best-practices skills/rust-review skills/rust-port ~/.agents/skills/ For Claude Code use ~/.claude/skills/ instead. Check for existing folders before copying; restart or reload the agent, then request a review of a specific Rust file, crate or diff. Rust and Cargo are needed for tool checks; reading-only review remains supported when unavailable.
Author
morganlinton
Publisher
Community
Last updated
Oct 27, 2026
Quick brief

Use BeautifulRust’s rust-review skill when an agent must review a specified Rust file, crate, module or pull-request diff and return prioritized findings with source rules and concrete fixes. Invoke it when a normal compiler or Clippy run cannot explain API design, soundness, error handling and maintainability tradeoffs in the context of the code.

How it works

What this skill actually does

Inputs and setup

Provide the repository and exact review scope. Install the complete upstream skill folders and references as described in the pinned README. The rust-best-practices companion supplies rule references; rust-port is distributed alongside it, but this listing covers the review workflow. Use a coding agent that reads the Agent Skills format. A Rust toolchain and Cargo enable mechanical checks.

Review workflow

  1. Read the requested scope, Cargo.toml, edition and minimum supported Rust version. State whether the target is a library or application. For a diff, inspect changed lines and consequences rather than expanding automatically to the whole repository.
  2. When tools are available, run cargo fmt --check, cargo clippy --all-targets --all-features -- -W clippy::pedantic, and cargo test from the crate root. State which checks actually ran; keep tool output separate from conclusions that require judgment.
  3. Inspect correctness and soundness first, followed by error handling, public API design, idiom, documentation and tests. Consult bundled references for uncertain rules and the Bevy reference when appropriate.
  4. Return Must fix, Should fix and Consider findings, followed by what the code already does well. Each finding identifies a file and line, cites the relevant rule and source, explains the consequence, and shows the smallest proposed change. Group repeated issues and respect documented intentional behavior.

Output and boundary

The deliverable is a proportionate review report for the named scope. Offer concrete fixes without rewriting files unless the user requests implementation. Suggest the upstream lint configuration when relevant rather than installing or changing project policy automatically. Do not claim that checks passed when they were unavailable. This is a reusable Rust review procedure, with review criteria and an output contract, rather than a listing for the Rust language, Clippy or a general coding agent.

Framework: Multi-Framework. Upstream deliberately supports several Agent Skills runtimes; no single runtime is central to this workflow. Metadata and source invocation were inspected, but installation, Rust execution and security review were not performed in this intake.

Sources: pinned review skill and pinned installation documentation.