run-checks
Skill1 starsChanged 6 months agoMITView on GitHub
Runs fmt, clippy, and tests after modifying the Rust implementation, or before committing. Use when asked to "run checks", "cargo check", "run checks", or "make CI pass".
6 other projects use a version of this.
Adopted by
Most recently taken up by
- erikunha/vault-of-locitheir own version, first seen Nov 16, 2026
- agent-ecosystem/agent-skill-implementationtheir own version, first seen Nov 8, 2026
- aniketshukla1/sdlc-kittheir own version, first seen Nov 8, 2026
- hashicorp/design-systemtheir own version, first seen Oct 13, 2026
- fws94/product9-token-savertheir own version, first seen Oct 11, 2026
- thinkyou0714/codex-toolkittheir own version, first seen Jul 3, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- hashicorp/design-system★ 519same name
- agent-ecosystem/agent-skill-implementation★ 6same name
- aniketshukla1/sdlc-kit★ 1same name
- fws94/product9-token-saver★ 1same name
- erikunha/vault-of-loci★ 0same name
- thinkyou0714/codex-toolkit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- validate-mappingsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
If this fails, run cargo fmt and then re-verify.
- Very specific: line 28
If this fails, fix each clippy finding.
- Very specific: line 29
When suppressing with #[allow(...)], always include a reason comment.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Steps
Execute the following in order. If a step fails, fix the issue before proceeding to the next step.
1. Format check
cargo fmt --checkIf this fails, run cargo fmt and then re-verify.
2. Clippy (warnings as errors)
cargo clippy -- -D warningsIf this fails, fix each clippy finding.
When suppressing with #[allow(...)], always include a reason comment.
3. Tests
cargo testFix any failing tests. If snapshots (insta) were updated, run cargo insta review to inspect the diff before accepting.
Completion condition
Report completion once all 3 steps pass with exit code 0.
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.

