rust-style

Enforce idiomatic Rust coding style guidelines on code modifications.

34|1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/uwu/flora --skill rust-style
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-style
Source: https://github.com/uwu/flora/tree/main/.agents/skills/rust-style
Command: npx skills add https://github.com/uwu/flora --skill rust-style

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures consistency and maintainability in Rust codebases by automatically enforcing a predefined set of idiomatic coding style rules.

Core Features & Use Cases

  • Enforces idiomatic Rust: Promotes the use of for loops, let...else, explicit matching, variable shadowing, newtypes, and discourages unnecessary comments and wildcard matches.
  • Improves Code Readability: Leads to cleaner, more predictable, and easier-to-understand Rust code.
  • Use Case: Integrate this skill into your CI/CD pipeline to automatically check and enforce coding standards on all new Rust pull requests, preventing style deviations before they merge.

Quick Start

Apply the rust-style skill to review and refactor the provided Rust code snippet for adherence to best practices.

Frequently Asked Questions about rust-style

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

FAQPage Schema
How do I enforce idiomatic Rust coding style in my project?

Idiomatic Rust uses specific patterns like for loops over iterators, let...else for early returns, and explicit variable destructuring. Enforcing these coding style guidelines leads to cleaner, more predictable, and easier-to-understand code.

What are the best practices for Rust pattern matching and variable declaration?

Rust best practices include using explicit matching, avoiding wildcard matches, and applying let...else for early returns. You should also use explicit destructuring and variable shadowing to maintain code readability and predictability.

Can I integrate Rust linter rules into a CI/CD pipeline?

Yes, you can integrate these Rust coding style rules into a CI/CD pipeline to automatically check pull requests. This prevents style deviations from merging by enforcing standards on all new Rust code modifications.

Does this Rust style guide require specific dependencies or components?

No specific dependencies are required to apply these Rust style guidelines. The skill operates using reference components to analyze and enforce coding best practices directly on your provided Rust code snippets.

When should I avoid using wildcard matches in Rust?

You should avoid wildcard matches in Rust to ensure explicit destructuring and pattern matching. Discouraging wildcards enforces a comprehensive set of idiomatic coding style rules that improve code quality and maintainability.

How do I refactor Rust code to use let...else for early returns?

To refactor Rust code for early returns, replace verbose if-let patterns with the let...else statement. This enforces idiomatic control flow, ensuring cleaner variable declaration and improved code readability.