rust-conventions

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.

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.

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.

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.

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.