rust-conventions

Enforce Rust project conventions with cargo fmt, clippy, and test checks.

1|Updated Nov 25, 2025

Search Tags:#linting #formatting #rust #conventions #cargo #ci

Ready to run

npx skills add https://github.com/89jobrien/dotfiles --skill rust-conventions-89jobrien

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rust-conventions
Source: https://github.com/89jobrien/dotfiles/tree/main/dot-claude/skills/rust-conventions
Command: npx skills add https://github.com/89jobrien/dotfiles --skill rust-conventions-89jobrien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Crates and workspaces often drift from recommended Rust practices, leading to CI failures, flaky builds, and maintenance headaches. This Skill provides a standardized set of checks and guidelines to keep Rust projects consistent and reliable.

Core Features & Use Cases

Enforce edition consistency by ensuring Cargo.toml uses edition = "2024" and validating it across crates.
Run deterministic quality gates with cargo fmt --check, cargo clippy -- -D warnings, and cargo test (workspace-wide when needed).
Maintain workspace integrity by verifying correct [workspace] members, referencing dependencies, and preventing common rust project pitfalls.

Quick Start

Run the convention checks across your Rust workspace using cargo fmt, cargo clippy, and cargo test to validate and harden your CI flow.

Frequently Asked Questions about rust-conventions

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

FAQPage Schema

How do I enforce Rust conventions to prevent CI failures in my workspace?▼

To enforce Rust conventions and prevent CI failures, run deterministic quality gates using cargo fmt --check and cargo clippy with -D warnings across your workspace. This standardizes code formatting and linting to keep crates reliable.

What does cargo clippy -D warnings do for Rust project consistency?▼

Running cargo clippy with -D warnings enforces Rust project consistency by treating all linter warnings as hard errors. This prevents code drift and ensures crates maintain recommended practices during feature work and CI runs.

How do I validate workspace integrity and edition consistency in Rust?▼

Validate Rust workspace integrity by verifying correct [workspace] members in Cargo.toml and ensuring edition = "2024" is consistent across all crates. This prevents common project pitfalls and configuration drift.

Can I use cargo nextest to speed up Rust convention checks?▼

Yes, you can use cargo nextest as an optional alternative to cargo test to speed up Rust convention checks. It accelerates test execution while still validating workspace-wide operations and maintaining CI reliability.

Why does my Rust crate drift from recommended practices during feature work?▼

Rust crates drift from recommended practices due to inconsistent formatting, ignored clippy warnings, and unverified workspace configurations. Applying standardized checks via cargo fmt, clippy, and test prevents this maintenance overhead.