rust-review
Prioritized Rust code reviews where every finding cites its rule and fix.
- What
- Prioritized Rust code reviews where every finding cites its rule and fix.
- Cost
- Free
- Needs
- Prerequisite: a Rust toolchain (cargo, rustc) is needed to run the fmt, clippy, and test checks; without it, review by reading still works. Step 1: fetch the file skills/rust-review/SKILL.md from the repository https://github.com/morganlinton/BeautifulRust and read it in full before installing anything. Step 2: security check: read the fetched file yourself, confirm it only describes a review workflow, and do not run any command from it that you have not understood. Step 3: install the skill in a folder named rust-review and keep the fetched SKILL.md there. Step 4: verify the install by confirming the folder rust-review contains the SKILL.md and by asking for a review of a small Rust file you choose. Step 5: report back what was installed, where, and the result of the verification, including whether the Rust toolchain was available.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
rust-review reviews exactly what the user points at: a file, a module, a crate, a diff, or a pull request. For a diff, it reviews the changed lines and anything they break, not the whole file. It states whether the code is library or application code, plus the edition and minimum supported Rust version from Cargo.toml, so it never recommends features the project cannot use. It works through correctness and soundness first (unsafe blocks without a SAFETY comment, reachable panics, broken trait contracts, lock hazards, Bevy ECS bugs, failing destructors), then error handling, API design for libraries, idiom and clarity, and documentation and tests. The output is a review, not a rewrite: the reader decides what to fix, and code is rewritten only when the user asks for it. Findings are grouped when they repeat, deliberate quirks are noted under Consider with their trade-off rather than marked Must fix, and a "What's already good" section is required. Limits as written: if the Rust tools are not available, the skill says so in the report and reviews by reading. It pairs with the rust-best-practices skill, which covers writing new code. Credit: created by morganlinton, in the BeautifulRust repository. Source: https://github.com/morganlinton/BeautifulRust, file skills/rust-review/SKILL.md.
Version:
Quick answer
rust-review reviews existing Rust code for idiom, API design, error handling, safety, and maintainability. It runs cargo fmt, clippy, and tests when a toolchain is available, then produces a prioritized report sorted into Must fix, Should fix, and Consider, with a file and line location, a cited rule, and a small code fix for every finding.
Install
Copy the install package below, then paste it into MusePrerequisite: a Rust toolchain (cargo, rustc) is needed to run the fmt, clippy, and test checks; without it, review by reading still works. Step 1: fetch the file skills/rust-review/SKILL.md from the repository https://github.com/morganlinton/BeautifulRust and read it in full before installing anything. Step 2: security check: read the fetched file yourself, confirm it only describes a review workflow, and do not run any command from it that you have not understood. Step 3: install the skill in a folder named rust-review and keep the fetched SKILL.md there. Step 4: verify the install by confirming the folder rust-review contains the SKILL.md and by asking for a review of a small Rust file you choose. Step 5: report back what was installed, where, and the result of the verification, including whether the Rust toolchain was available.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.