release-readiness
Skill1 starsChanged 4 months agoMITView on GitHub
Use when preparing to tag, publish, or promote a stringdb-link build.
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 43 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Run make ci-local; build/validate the container (make docker-build plus any docker-*-config validation targets the Makefile exposes).
- Very specific: line 14
Verify single-source versioning (../genefoundry-router/docs/VERSIONING-STANDARD-v1.md): the version comes from package metadata and …
- Distinctive: line 15
Check README / CHANGELOG, MCP safety language, and deployment docs for drift.
“Common” is measured: kept by at least 6 in 10 of the 43 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
Release Readiness
Follow AGENTS.md first.
Workflow
- Confirm the worktree holds only intended release changes.
- Run
make ci-local; build/validate the container (make docker-buildplus anydocker-*-configvalidation targets the Makefile exposes). - Verify single-source versioning (../genefoundry-router/docs/VERSIONING-STANDARD-v1.md): the version comes from package metadata and
serverInfo.versiondoes not leak the framework version; the version guard test passes. - Check README / CHANGELOG, MCP safety language, and deployment docs for drift.
- Confirm any destructive MCP tools remain opt-in and the container overlays stay hardened (../genefoundry-router/docs/CONTAINER-HARDENING-STANDARD-v1.md).
- Record residual risks before handoff.
Other versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 9
- berntpopp/genefoundry-router★ 617% same
- berntpopp/hpo-link★ 196% same
- berntpopp/mgi-link★ 196% same
- berntpopp/clingen-link★ 096% same
- berntpopp/gnomad-link★ 096% same
- berntpopp/hgnc-link★ 096% same
- berntpopp/mondo-link★ 096% same
- berntpopp/spliceailookup-link★ 096% same
- berntpopp/vep-link★ 096% same
Wrote their own version · 35
- dotnet/maui★ 23ksame name
- AIEraDev/Clypra★ 3.3ksame name
- jordanhubbard/nanolang★ 628same name
- petrkindlmann/qa-skills★ 209same name
- colasama/MahoShojo-Generator★ 167same name
- MRCalderon3D/everything-game-dev-code★ 91same name
- Azure/odinforazurelocal★ 20same name
- jpantsjoha/ai-native-developer-experience★ 13same name
- NotHarshhaa/devops-skills★ 8same name
- 05-deepak-patidar/claude-skills★ 4same name
25 more not listed
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.
Used alongsideProjects with it also use test-strategy, systematic-debugging and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jarosser06Skilltest-strategy
Plans pytest test strategies for Drift's 90%+ coverage requirement using coverage analysis, edge case identification, and test suite design. Use when determining what tests to write, analyzing coverage gaps, or planning test strategies.
Also in 3 projects that use this
OpenAISkillsystematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Also in 5 projects that use this
- OpenAISkill
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Also in 4 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 6 projects that use this
- +1 more from openai
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ci-failure-triageSkill
- code-quality-reviewSkill
- dependency-cve-sweepSkill
- fastapi-route-changeSkill
- fleet-standard-adoptionSkill
- mcp-tool-changeSkill
- security-reviewSkill
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.