release-readiness
Skill0 starsChanged 13 days agoMITView on GitHub
Assess whether a change is ready for a tagged release or deployment. Use before publishing a package, shipping a production build, or announcing a new version.
48 other projects use a version of this.
Adopted by
Most recently taken up by
- HumSaw/shipwright-skillstheir own version, first seen Nov 8, 2026
- RaditteAnggoro/skill-for-lazy-developertheir own version, first seen Nov 8, 2026
- nledford/engineering-review-boardtheir own version, first seen Nov 3, 2026
- pulsejet/memoriestheir own version, first seen Nov 1, 2026
- florian101010/awesome-agentic-AI-coding-templatetheir own version, first seen Nov 1, 2026
- Kin9Zeus/senior-engineer-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use dependency-cve-sweep, fleet-standard-adoption and 10 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.
berntpoppSkilldependency-cve-sweep
Use when handling Dependabot PRs, CodeQL/Trivy alerts, or doing a routine dependency/CVE sweep for this repo.
Also in 12 projects that use this
- berntpoppSkill
fleet-standard-adoption
Use when bringing this repo into compliance with a GeneFoundry fleet standard (tool-naming, response-envelope, container-hardening, versioning, MCP transport, or logging) or closing its tracking issue.
Also in 12 projects that use this
IgorGanapolskySkillci-failure-triage
Triage a CI / PR check failure by READING the failure body before forming any hypothesis. Triggered whenever a required check is red, a PR is BLOCKED, a merge won't land, or you're about to call a failure "transient", "flaky", "stale", or "orphaned". Prevents dismissing a real failure (e.g. real CodeQL security alerts) as noise.
Also in 14 projects that use this
VersoXBTSkillcode-quality-review
Perform structured code reviews enforcing quality standards, naming conventions, architecture patterns, and team agreements. Use when the user says 'review this code', 'code review', 'check quality', 'review my PR', 'what's wrong with this', 'improve this code', 'review before merge', 'peer review', or 'audit this'. Also triggers on 'code quality', 'review standards', 'enforce conventions', 'tech debt check', 'lint review', or when user completes a significant code change.
Also in 12 projects that use this
ffsshhttiikkSkillunit-testing
Unit testing best practices and patterns
Also in 3 projects that use this
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 4 projects that use this
- +2 more from berntpopp
Other versions48 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 48
- dotnet/maui★ 23ksame name
- pulsejet/memories★ 3.9ksame name
- AIEraDev/Clypra★ 3.4ksame name
- jordanhubbard/nanolang★ 629same name
- petrkindlmann/qa-skills★ 209same name
- colasama/MahoShojo-Generator★ 167same name
- MRCalderon3D/everything-game-dev-code★ 105same name
- Azure/odinforazurelocal★ 20same name
- jpantsjoha/ai-native-developer-experience★ 13same name
- nledford/engineering-review-board★ 11same name
38 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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-skill-auditSkill
- api-contract-checkSkill
- build-rescueSkill
- change-narrativeSkill
- context-handoffSkill
- data-quality-gateSkill
- dataset-workshopSkill
- dependency-careSkill
- docs-syncSkill
- experiment-ledgerSkill
- failure-forensicsSkill
- model-diff-reviewSkill
- model-eval-designSkill
- multi-agent-crosscheckSkill
- parallel-task-designSkill
- performance-proofSkill
- repo-scoutSkill
- research-evidence-mapSkill
- review-lensSkill
- safe-migrationSkill
- security-surfaceSkill
- spec-firstSkill
- sql-integrity-checkSkill
- test-driven-changeSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 47 edited versions we read keep these.
3
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 12
Run the documented validation suite: tests, type checking, linting, build/package, and security checks relevant to the project.
- Distinctive: line 13
Verify distribution contents: no debug credentials, local paths, temporary datasets, internal notes, build artifacts that should not ship, …
- Distinctive: line 14
Check compatibility and rollback: database changes, environment variables, config defaults, API changes, and package …
“Common” is measured: kept by at least 6 in 10 of the 47 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
Procedure
- Identify what is being released, release method, target environment, versioning rules, and person authorized to approve publication.
- Inspect diff, changelog, version metadata, lockfiles, release notes, migration instructions, supported platforms, and known issues.
- Run the documented validation suite: tests, type checking, linting, build/package, and security checks relevant to the project.
- Verify distribution contents: no debug credentials, local paths, temporary datasets, internal notes, build artifacts that should not ship, or unlicensed assets.
- Check compatibility and rollback: database changes, environment variables, config defaults, API changes, and package installation/uninstallation.
- Validate release notes against the real diff. Clearly separate new features, fixes, breaking changes, and known limitations.
- Present a gate decision: ready, blocked, or ready with explicitly accepted risk. Include proof and the owner of unresolved items.
Approval boundary
Prepare release commands and artifacts, but stop before creating a tag, publishing a package, deploying, or sending external announcements unless the user explicitly authorizes that exact action.
Deliverable
Checklist of passed/failed/not-run checks, changed version, release notes draft, unresolved risk, rollback path, and the next authorized action.
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.