lint-rust
Skill15 starsChanged 5 months agoMITView on GitHub
Run comprehensive linting and static analysis on Rust code including clippy, format check, security audit, supply chain, and unused dependencies. Use before committing, during CI, or when reviewing code quality. Triggers: "lint rust", "clippy", "static analysis", "code quality".
- Installs packages
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- anti-ai-slopSkill
- architecture-diagramSkill
- atomic-commitSkill
- build-rustSkill
- codacySkill
- crates-io-name-checkSkill
- dora-reportSkill
- goap-agentSkill
- harnessSkill
- issue-triageSkill
- metrics-reporterSkill
- privacy-firstSkill
- release-rustSkill
- reviewing-pull-requestsSkill
- secret-lintSkill
- self-fix-loopSkill
- skill-creatorSkill
- skill-evaluatorSkill
- stacked-prsSkill
- task-decompositionSkill
- test-rustSkill
- tokio-performanceSkill
- triz-analysisSkill
- triz-solverSkill
- verify-actionsSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Run comprehensive linting and static analysis on Rust code.
- Distinctive: line 27
When reviewing code quality
- Distinctive: line 28
After adding new dependencies
- Very specific: line 71
All clippy lints pass with -D warnings
- Distinctive: line 73
No known security vulnerabilities
- Distinctive: line 74
All licenses are allowed
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: lint-rust
Purpose
Run comprehensive linting and static analysis on Rust code.
Trigger Conditions
- Before committing code
- During CI/CD pipeline
- When reviewing code quality
- After adding new dependencies
Prerequisites
cargo clippy(bundled with Rust)cargo audit(cargo install cargo-audit)cargo deny(cargo install cargo-deny)cargo machete(cargo install cargo-machete)
Steps
1. Clippy strict mode
cargo clippy --workspace --all-targets --all-features -- -D warnings2. Format check
cargo fmt --all -- --check3. Security audit
cargo audit4. Supply chain check
cargo deny check5. Unused dependencies
cargo macheteSuccess Criteria
- All clippy lints pass with
-D warnings - Format is consistent
- No known security vulnerabilities
- All licenses are allowed
- No unused dependencies
Related Skills
build-rust- Building the projecttest-rust- Running testsrelease-rust- Release preparation
Rationalizations
| Rationalization | Reality |
| "Clippy passes, so the code is clean." | Clippy alone doesn't check licenses, security, or unused deps. Run the full suite. |
| "cargo audit shows no advisories, we're safe." | Audit only checks known advisories. Also run cargo-deny for license compliance. |
| "I'll skip machete — unused deps aren't a big deal." | Unused deps increase compile time and attack surface. Remove them. |
Red Flags
- Running only
cargo clippywithoutcargo fmt --check - Skipping
cargo auditorcargo denyin CI - Ignoring
-D warningsflag (allows warnings to accumulate)
References
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.