pre-release-check
Skill88 starsChanged 8 months agoMITView on GitHub
Run full quality gate before release — fmt, clippy, test, mutants, similarity, coupling.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- willdady/platypustheir own version, first seen Nov 15, 2026
- getstackit/stackittheir own version, first seen Oct 30, 2026
- use-novamira/novamiratheir own version, first seen Oct 8, 2026
- lezama/openclawptheir own version, first seen May 18, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- use-novamira/novamira★ 758same name
- willdady/platypus★ 130same name
- getstackit/stackit★ 32same name
- lezama/openclawp★ 1same 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 repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- bug-fixSkill
- deploy-checkSkill
- dev-setupSkill
- orchestratorSkill
- qa-pipelineSkill
- refactor-analysisSkill
- refactorSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 38
Ensure no regression from previous grade.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Pre-Release Check
Full quality gate to run before tagging a release.
Steps (sequential)
- Basic quality:
cargo fmt --check cargo clippy -- -D warnings cargo test - Mutation testing (core modules):
Review missed mutants. Add tests for any critical logic that survived mutation.cargo mutants --timeout 60 --jobs 4 \ --file src/parser.rs --file src/reports.rs \ --file src/models/ --file src/pricing.rs \ --file src/billing_blocks.rs - Code similarity:
Flag any 95%+ duplicates that weren't addressed.similarity-rs ./src --min-tokens 50 - Coupling analysis:
Ensure no regression from previous grade.cargo coupling --exclude-tests --check --min-grade C - Dry-run publish:
cargo publish --dry-run - Report: Summarize pass/fail for each gate. Block release if mutants expose critical untested logic.
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.

