rust

Review Rust code diffs for correctness, safety, and performance anti-patterns.

Updated May 15, 2026
One-click install
npx skills add https://github.com/mattnowdev/super-review --skill rust-mattnowdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rust
Source: https://github.com/mattnowdev/super-review/tree/main/skills/rust
Command: npx skills add https://github.com/mattnowdev/super-review --skill rust-mattnowdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps review Rust changes by surfacing subtle correctness, concurrency, and API-design hazards that automated linting often misses.

Core Features & Use Cases

  • Correctness & invariants: Flags panic-prone unwrap/expect usage and missing invariant documentation.
  • Concurrency & cancellation safety: Reviews tokio/async patterns for cancellation-unsoundness, locking contention, and spawn handling.
  • Modern Rust ecosystem hygiene: Detects inefficient ownership/cloning patterns, unsafe trait misdocumentation, and error-type design issues.

Quick Start

Ask the AI to review the Rust diff and produce an evidence-quoted checklist focused on async cancellation safety, unsafe invariants, and error-handling correctness.

Frequently Asked Questions about rust

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

FAQPage Schema
How do I review Rust async code for cancellation safety and tokio anti-patterns?▼

Review Rust async code by checking tokio spawn and join handling for cancellation-unsoundness, detecting locking contention in Arc<Mutex> misuse, and verifying task lifecycle correctness in the diff.

What is the best way to check Rust diffs for unsafe code and ownership borrowing issues?▼

Check Rust diffs by scanning unsafe trait and block documentation for missing invariants, identifying inefficient clone and borrow patterns, and validating ownership transfers in the modified code.

How do I find panic-prone unwrap and expect usage in my Rust code changes?▼

Find panic-prone unwrap and expect usage by applying checklist-style detection to Rust code diffs, flagging missing invariant documentation, and requiring typed error guidance for robust error handling.

Does this code review approach work with Cargo.toml and Cargo.lock updates?▼

Yes, this code review approach applies when changes include *.rs files or updates to Cargo.toml and Cargo.lock, ensuring dependency modifications and Rust source changes are reviewed for correctness.

Why does automated linting miss Rust concurrency and error modeling hazards?▼

Automated linting misses Rust concurrency and error modeling hazards because it cannot understand subtle cancellation-unsoundness, complex Arc<Mutex> contention, or typed error design flaws in async workflows.