release-check
Skill12 starsChanged 46 days agoMITView on GitHub
Pre-release gate covering tests, build, docs, changelog, privacy, security, and sprint closure. Delegates to `verify-build-works`, `secrets-scan`, and `privacy-audit` rather than re-checking by hand. Run before tagging a release, before closing a sprint, before a first deploy, and when the user says "tá pronto pra lançar?", "posso subir isso?", "fecha a versão", "dá pra publicar?".
14 other projects use a version of this.
Adopted by
Most recently taken up by
- hhopke/intervals-icu-mcptheir own version, first seen Nov 8, 2026
- langchain-ai/design-agenttheir own version, first seen Oct 25, 2026
- phatysddev/skillstheir own version, first seen Oct 9, 2026
- ruby/rdoctheir own version, first seen Oct 8, 2026
- thoughtfulllc/gridlandtheir own version, first seen Oct 8, 2026
- Thank-you-Linus/Linus-Dashboardtheir own version, first seen Oct 8, 2026
Used with
Projects with it also use review.
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.
SentrySkillreview
Fixture review skill.
Also in 5 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- samuelgursky/davinci-resolve-mcp★ 4ksame name
- ruby/rdoc★ 930same name
- langchain-ai/design-agent★ 596same name
- thoughtfulllc/gridland★ 363same name
- Thank-you-Linus/Linus-Dashboard★ 214same name
- hhopke/intervals-icu-mcp★ 121same name
- acailic/agent_debugger★ 9same name
- phatysddev/skills★ 8same name
- YorkWong1995/OPC-Harness★ 4same name
- broomva/lago★ 2same name
4 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.
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- business-plan-impact-reviewSkill
- codemapSkill
- cost-watchdogSkill
- daily-standupSkill
- decision-logSkill
- deploy-vercel-supabaseSkill
- feature-scaffoldSkill
- first-100-usersSkill
- grow-sustainablySkill
- multi-ai-reviewSkill
- os-self-testSkill
- pitchSkill
- plain-portuguese-explainerSkill
- privacy-auditSkill
- processizeSkill
- product-briefSkill
- project-genesisSkill
- prototype-labSkill
- registry-pickSkill
- research-wavesSkill
- rollback-safeSkill
- secrets-disciplineSkill
- secrets-scanSkill
- sprint-managementSkill
- sprint-roadmapSkill
- usage-monitorSkill
- verify-build-worksSkill
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 12 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 10
Do not re-implement checks that already have a skill.
“Common” is measured: kept by at least 6 in 10 of the 12 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 Check
Required checks
Do not re-implement checks that already have a skill. Delegate, then record the verdict.
| Check | Delegate to | Blocking? |
| Tests pass | project test runner | yes |
| Build + dev server + main flow load | verify-build-works | yes |
| No leaked secrets or credentials | secrets-scan | yes |
| Personal-data changes reviewed | privacy-audit | yes, when applicable |
| Changelog updated | — | yes |
| Codemap em dia | codemap — node scripts/codemap.js --check | yes |
| Sprint doc updated | sprint-management | yes |
| Session logs or ADRs for important decisions | decision-log | warning |
| OS structure still coherent | os-self-test | warning |
| Coordinator review complete | coordinator-agent | yes |
For a hard-to-reverse release decision (first public launch, pricing change shipping with the release, irreversible migration), run multi-ai-review before issuing a verdict.
Output
Release candidate:
Blocking issues:
Warnings:
Verdict: RELEASE | RELEASE_WITH_NOTES | BLOCKDoes 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.