release-readiness-checklist
Skill1 starsChanged 28 days agoMITView on GitHub
Produce an evidence-based go/no-go release readiness report covering test results, open defects, coverage of changes, and risks.
In this repository16 other files it gives its agents.
- accessibility-auditSkill
- api-test-generatorSkill
- automation-code-reviewSkill
- bug-report-writerSkill
- ci-cd-and-test-dataSkill
- device-cloud-setupSkill
- flaky-test-triageSkill
- framework-scaffolderSkill
- greenbuild-getting-startedSkill
- llm-app-testingSkill
- mobile-automationSkill
- performance-test-starterSkill
- regression-health-digestSkill
- test-plan-from-requirementsSkill
- tools-and-librariesSkill
- visual-testingSkill
The file
Files
Release readiness checklist
- Identify the release (version, scope or changelog, target date) and the go/no-go criteria saved in memory. If there are none, propose defaults: no open P0/P1, regression pass rate of at least 98% with failures explained, and every new feature has test evidence.
- Gather evidence: latest regression and smoke results, open defects by severity, the list of changes (PRs/tickets), and performance or security scan results if they exist.
- Map the changes to tests: for each change, record Tested? (Y/N/partial) and the evidence link.
- List what was not tested, and why.
- Risks: top risks, each with a mitigation (feature flag, monitoring, rollback plan).
- Output: Recommendation: GO / GO with conditions / NO-GO at the top, then a checklist table (criterion | status | evidence), open blockers, and rollback readiness.
- The final decision belongs to the human. Never state "approved" yourself.
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.