rust-cargo-hygiene

name

rust-cargo-hygiene

description

Audit Cargo.toml, feature flags, MSRV, lints, and crate-level configuration for release readiness on changed manifests or whole-repo baseline audits when explicitly requested. USE FOR: Cargo.toml review, feature flag design, default-features gating, dev/build/runtime dependency placement, dependency version specifiers, MSRV pin, edition, [lints] table, clippy.toml/rustfmt.toml, crate-level deny/warn lints (including unsafe_code = forbid), workspace inheritance, [package.metadata.docs.rs] config, semver-sensitive Cargo manifest changes, preparing a crate release. DO NOT USE FOR: source-level Rust review (use rust-production-review or other Rust skills), CI/CD workflow logic, non-Rust packaging, or unrelated unchanged manifests unless a baseline audit is requested. Use when this capability is needed.

rust-cargo-hygiene

Audit Cargo.toml, feature flags, MSRV, lint configuration, and other crate-level settings for clarity, semver discipline, and release readiness.

Manifest mistakes break downstream builds quietly: an unintended default-features = true, a missing dev-only dependency move, or a slipping MSRV often only surfaces on a user's machine. Treat the manifest as part of the public API.

Scope

Focus on newly added or modified files such as:

• Cargo.toml (root, workspace, and per-crate)
• Cargo.lock only when the lock file is committed (binary crates or workspace policy)
• clippy.toml, rustfmt.toml, .cargo/config.toml
• crate-root attributes (#![deny(...)], #![warn(...)], #![forbid(...)])
• rust-toolchain.toml

Scope Modes

Default mode:

• Audit newly added or modified manifests, toolchain files, lint configuration, and crate-root attributes.