release-check
Skill1 starsChanged 2 months agoMITView on GitHub
Use before deploying, publishing, tagging, or announcing a release to determine whether the exact release candidate is ready, conditionally ready, or blocked.
15 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 versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- samuelgursky/davinci-resolve-mcp★ 4.1ksame name
- ruby/rdoc★ 930same name
- langchain-ai/design-agent★ 619same name
- thoughtfulllc/gridland★ 363same name
- Thank-you-Linus/Linus-Dashboard★ 214same name
- hhopke/intervals-icu-mcp★ 121same name
- lglucas/ai-dev-operating-system★ 12same name
- acailic/agent_debugger★ 9same name
- phatysddev/skills★ 8same name
- YorkWong1995/OPC-Harness★ 4same name
5 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 repository10 other files it gives its agents.
- ci-repairSkill
- feature-qaSkill
- impact-checkSkill
- indie-viral-principlesSkill
- onboarding-flows-designSkill
- safe-refactorSkill
- ui-mobile-fondationsSkill
- ux-psychologie-premiumSkill
- verified-featureSkill
- verified-fixSkill
The file
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 13 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 12
REQUIRED SUB-SKILLS: Use impact-check, verification-before-completion, and feature-qa for material customer-facing changes.
- Very specific: line 31
Never display secret values.
- Distinctive: line 35
Use fresh evidence from the exact candidate:
“Common” is measured: kept by at least 6 in 10 of the 13 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
Overview
Produce an evidence-based go/no-go verdict for one exact release candidate. This workflow does not deploy, tag, publish, push, or approve on the user’s behalf.
REQUIRED SUB-SKILLS: Use impact-check, verification-before-completion, and feature-qa for material customer-facing changes.
1. Pin the Candidate
Record the source commit, comparison base or previous release, target environment, version, artifact identity/checksum, and build provenance.
The artifact and all evidence must refer to the same source state. A dirty working-tree build, mismatched CI commit, or unknown artifact is immediately BLOCKED until rebuilt from approved source.
2. Inventory Release Risk
Inspect the complete release diff and classify:
- behavior and public-contract changes
- database migrations and persistent data
- dependencies, lockfiles, generated artifacts, and supply-chain inputs
- configuration, secrets presence, permissions, flags, and infrastructure
- compatibility, rollout order, external consumers, and rollback constraints
- user-visible workflows, known issues, and support impact
Never display secret values. Use impact-check for material or uncertain blast radius.
3. Verify Required Gates
Use fresh evidence from the exact candidate:
- repository-required tests, lint, type checks, builds, and CI checks
- artifact installation/startup and production-like smoke tests
- security, dependency, contract, compatibility, or performance checks required by the project
- migration rehearsal, data-integrity checks, backup restore, and rollback rehearsal where data changes
- rollout plan, owners, observability, alerts, abort thresholds, and recovery runbook
- versioning, changelog, release notes, and documentation required by repository policy
For a material customer-facing feature, run feature-qa. Only the user can mark its manual scenarios PASS; green automation cannot substitute for acceptance.
Missing irrelevant gates may be marked N/A with a reason. Missing required evidence is not a pass.
4. Reconcile Risks
List every known issue with severity, affected users, mitigation, owner, rollback trigger, and explicit acceptance status.
A destructive or irreversible migration without rehearsed recovery, an unresolved security/data-integrity risk, red required CI, failed acceptance, unknown artifact provenance, or unverified rollback is blocking.
Verdict
Use exactly one:
READY— every required gate passes for the exact candidate and no unresolved material risk remainsREADY WITH RISKS— only non-blocking risks remain, each explicitly accepted with mitigation and rollbackBLOCKED— any required gate, approval, provenance, recovery path, or material risk is unresolved
Output
Verdict
<READY | READY WITH RISKS | BLOCKED and rationale>
Candidate
<commit, version, artifact, target>
Change inventory
<material release risks>
Gate evidence
<required gate, command/artifact, outcome>
Accepted risks
<owner, mitigation, rollback trigger>
Blockers
<owner and evidence needed>
Release and rollback
<ordered plan, observability, abort criteria>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.

