Skill: Clippy Customization #13

Problem

As of #12 , the rust-best-practice skill recommends running cargo clippy, but different projects have different needs for lint configuration. Some teams want to deny specific lint groups (e.g., clippy::pedantic), allow certain lints that produce false positives in their codebase, or enforce project-specific conventions via clippy attributes. There's no guidance on how to customize clippy behavior per project.

Proposed Skill

A clippy-customization skill that teaches the agent how to:

• Configure clippy via clippy.toml / .clippy.toml at the workspace root
• Use crate-level attributes (#![warn(...)], #![deny(...)], #![expect(...)]) appropriately
• Recognize common lint groups (clippy::pedantic, clippy::nursery, clippy::cargo) and when to enable them
• Suppress specific lints inline with #[expect(clippy::...)] and require a justification comment
• Respect existing project lint configuration rather than overriding it

Activation Trigger

Activate when the user asks about configuring clippy lints, suppressing warnings, or when a project has a clippy.toml present.

(This is not something we currently support, but it would be nice)