From rust-learning
This skill should be used when the user wants feedback on Rust code they have written. Use when the user asks to "review", "check", "look at", "critique", or "give feedback on" their code, or after they finish implementing something and want to know if it's idiomatic, correct, or could be improved. This is a teaching review — not a rewrite.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rust-learning:reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Review the user's Rust code for correctness, idioms, and learning opportunities.
Review the user's Rust code for correctness, idioms, and learning opportunities. This is a teaching review — the goal is understanding, not a perfect diff.
.unwrap() on None/Err that could realistically occur)? for error propagation,
match patterns, appropriate trait usage$ARGUMENTS or the current file in context
npx claudepluginhub eywalker/claude-marketplace --plugin rust-learningReviews Rust code for ownership, borrowing, lifetimes, error handling, trait design, unsafe usage, and common mistakes. Covers Rust 2024 edition patterns and modern idioms.
Guides writing idiomatic Rust code covering borrowing, error handling, performance, linting, testing, and documentation based on Apollo GraphQL's best practices handbook.
Audits Rust code for unsafe blocks, ownership and borrowing patterns, concurrency issues, error handling, and Cargo dependency vulnerabilities.