Review and refactor Rust code for ownership, error handling, and traits.
npx skills add https://github.com/tincopper/neeko --skill rust-patterns-tincopper
Please help me install this Agent Skill. Skill: rust-patterns Source: https://github.com/tincopper/neeko/tree/main/.claude/skills/rust-patterns Command: npx skills add https://github.com/tincopper/neeko --skill rust-patterns-tincopper
It helps you write Rust that is safer, clearer, and easier to maintain by replacing ad hoc coding habits with idiomatic patterns for ownership, errors, traits, concurrency, and module design.
Ask for a review or refactor of your Rust code that applies idiomatic ownership, error handling, trait usage, concurrency, and module organization best practices.
High-intent search queries and answers about installing and using this skill.
To refactor Rust code, you replace excessive cloning and unwrap calls with idiomatic ownership patterns, result-driven error propagation, and typed errors. This process enforces ownership safety and yields cleaner, production-ready modules.
The best way to handle errors in Rust is using result-driven propagation with typed library errors and application-friendly context. This typed error handling replaces panic-prone logic and improves overall application maintainability.
You need to use traits and generics for abstraction in Rust when designing architecture patterns that require flexible APIs. Modeling state with exhaustive enums and applying newtypes ensures type safety and minimal public interfaces.
To structure shared state and async tasks for concurrency safety in Rust, you organize channels and async tasks using practical patterns. This refactoring ensures concurrency-heavy systems maintain safe shared state management.
Yes, you can use idiomatic Rust patterns to review and improve existing applications, libraries, and modules. Reviewing enforces ownership safety, typed error handling, and minimal public APIs to enhance code quality.
CallMeLuigiv2Identify and explain Rust anti-patterns during code reviews.
Sake-TeamGuide idiomatic Rust patterns for ownership, error handling, traits, and concurrency.
Blake-JohnEnforce idiomatic Rust patterns for ownership, error handling, and concurrency.
MileniumTickApply idiomatic Rust best practices for ownership, borrowing, error handling, and testing.
