Apply Rust conventions to write idiomatic, safe, and maintainable .rs code.
npx skills add https://github.com/erichugy/agentic.skills --skill rust-erichugy
Please help me install this Agent Skill. Skill: rust Source: https://github.com/erichugy/agentic.skills/tree/main/rust Command: npx skills add https://github.com/erichugy/agentic.skills --skill rust-erichugy
Ensures Rust code is idiomatic, consistent, and safe by reducing bugs from ownership mistakes, inconsistent error handling, and style divergence across a codebase.
Review src/lib.rs and suggest changes to naming, error handling, ownership, formatting, and clippy warnings to make the code idiomatic and safe.
High-intent search queries and answers about installing and using this skill.
Idiomatic Rust code enforces snake_case for functions and modules, PascalCase for types, and UPPER_SNAKE_CASE for constants. It requires running cargo fmt and clippy checks to ensure consistent formatting and maintainable .rs source files across libraries and applications.
Error handling in Rust should use Result-based error propagation instead of unwrap or expect in production code. For idiomatic error management, apply thiserror or anyhow patterns to safely propagate errors through your application without panicking.
Managing Rust ownership and borrowing requires following guidance on module layout and concurrency best practices to avoid unnecessary clones and lock contention. Optimizing performance idioms like iterator usage and preallocation helps maintain safe, efficient memory management.
Yes, you can review and refactor existing .rs source files for safety by checking naming conventions, error handling, ownership, formatting, and clippy warnings. This process improves code maintainability and reduces bugs from ownership mistakes across your codebase.
Rust code fails clippy checks and cargo fmt standards when it diverges from idiomatic style rules like improper naming conventions, missing trait derivations, or suboptimal iterator usage. Enforcing required cargo fmt and clippy checks resolves these style divergences.
martimramosEnforce Rust testing, linting, and formatting standards via cargo commands.
RediSearchAutomate Rust unit and integration tests with cargo test.
svssdevaStandardize Rust code authoring and review with clippy-informed quality gates.
noh-rsReview Rust code against 179 idiomatic rules for ownership, errors, async, and API design.
