skills.rest
LudwigAJ
LudwigAJCOMMUNITY
Explore all skills by this author →
GitHub

rust-code-review

Review Rust source code for ownership, borrowing, lifetime, and error handling issues.

Updated Apr 8, 2026
Search Tags:#ownership#rust#clippy#borrowing#error-handling#code-review#unsafe
One-click install
npx skills add https://github.com/LudwigAJ/swell --skill rust-code-review-ludwigaj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rust-code-review
Source: https://github.com/LudwigAJ/swell/tree/main/.claude/skills/rust-code-review
Command: npx skills add https://github.com/LudwigAJ/swell --skill rust-code-review-ludwigaj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps reviewers catch correctness, safety, and API-design problems in Rust code before they reach production, especially issues that compile but still behave badly.

Core Features & Use Cases

  • Ownership and Borrowing: Finds clone-heavy fixes, lifetime mistakes, and reference-flow problems.
  • Error Handling: Flags unwrap and expect misuse, missing context, and weak error types.
  • Async and Concurrency: Checks blocking calls in async code, lock handling across await points, and Send/Sync issues.
  • Unsafe and Style Review: Verifies unsafe invariants, clippy patterns, imports, and public API design.
  • Use Case: Review a pull request in a Rust workspace and return actionable findings with file and line references.

Quick Start

Use the rust-code-review skill to review the changed Rust files in a pull request and report any ownership, borrowing, error-handling, async, unsafe, or trait-design issues you find.

Frequently Asked Questions about rust-code-review

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

FAQPage Schema
How do I review Rust code for ownership and borrowing mistakes before merging?▼

Review Rust code for ownership and borrowing by inspecting full functions to find clone-heavy fixes, lifetime mistakes, and reference-flow problems, producing actionable findings with file and line-specific severity labels.

What is the best way to check async Rust code for blocking calls and Send/Sync issues?▼

Checking async Rust code involves auditing lock handling across await points, verifying Send/Sync issues, and detecting blocking calls in async code to ensure safe concurrency before production deployment.

How do I audit unsafe Rust blocks and verify their invariants during a code review?▼

Auditing unsafe Rust blocks requires verifying unsafe invariants, checking public API design, and validating clippy patterns and imports to ensure safe usage and correct style across the workspace.

Does this Rust code review support Cargo.toml context checks and Rust 2021 edition idioms?▼

Yes, Rust code review supports Cargo.toml context checks and validates Rust 2021 or newer idiom usage across libraries and applications to ensure edition-aware reasoning and correct dependency configurations.

How do I flag unwrap and expect misuse in Rust error handling during a pull request?▼

Flag unwrap and expect misuse in Rust error handling by inspecting weak error types, identifying missing context, and verifying proper error propagation to generate line-specific severity findings.

Related Skills

Explore More Software Engineering Skills→
mscipiomscipio

ast-analyzer

Parse source code into Abstract Syntax Trees for symbol extraction and variable flow tracing.

Community
Advanced
HigorAlvesHigorAlves
4

inline-review

Convert structured JSON review findings into inline GitHub Pull Request comments.

Community
Intermediate
svssdevasvssdeva
1

Rust Engineer

Write idiomatic Rust 2021 code with ownership, error handling, and clippy validation.

Community
Advanced
Marwan78888Marwan78888
16

rust-engineer

Resolves Rust ownership, borrowing, and lifetime issues for memory-safe code.

Community
Advanced