release-readiness SKILL.md skillA
release-readiness from petrkindlmann/qa-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add petrkindlmann/qa-skills/release-readiness@v2.2Pins v2.2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- petrkindlmann/qa-skills
- Path
skills/release-readiness/SKILL.md- Versions recorded
- 5
- Latest version
- v2.2, committed Oct 21, 2026
- First version recorded
- May 30, 2026
- Size
- 28,568 bytes
- Repository stars
- 237
- License
- MIT
Validate release readiness with evidence-based go/no-go decisions. Covers go/no-go checklists, smoke test suite design, staged rollout validation, rollback criteria and procedures, and post-deployment verification. Ensures release confidence comes from data, not feelings. Use when: "release ready," "go/no-go," "smoke test," "release checklist," "rollback plan," "staged rollout," "canary deploy." Not for: safe-release techniques (flags, canary, dark launch) applied during the rollout itself —…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<objective> "I think it's fine" ships the bug that the rollback you never practiced can't undo at 6 PM on a Friday. This skill turns "ready to ship" into something measurable: a go/no-go checklist with evidence for each item, a sub-5-minute smoke suite, a staged rollout with metric-gated promotion, rollback thresholds defined before deploy, and post-deployment verification. Every section gives concrete criteria, not aspirations. </objective> --- ## Discovery Questions Check `.agents/qa-project-context.md` first — if it exists, use it and skip anything answered there. Then ask only what's missing. **Release cadence and process:** - How often do you release, and who makes the go/no-go call? (Continuous/daily/weekly vs engineering lead/QA lead/release manager — sets how heavyweight the checklist should be.) - Is there a release train schedule or is it ad-hoc? - How many environments exist between dev and production? (staging, pre-prod, canary) **Current state:** - What does the current go/no-go process look like, and is it documented? - Has a release ever been rolled back? How long did it take? (Reveals whether rollback is real or aspirational.) …
Read the whole file at its exact version.
How to install
mdr add petrkindlmann/qa-skills/release-readiness@sha256:601a498037d980daThe line at the top of this page pins the label v2.2, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_wahhul5tac4dphk3)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 30, 2026 and Oct 21, 2026, about one every 36 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.2 latest | 2026-10-21 | 417d49a | 28,568 B | A | view · diff |
| v2.1 | 2026-10-21 | b99ea46 | 27,974 B | A | view · diff |
| v2.0 | 2026-06-10 | 5e772b2 | 26,817 B | A | view · diff |
| v2.0 | 2026-06-10 | bcd1201 | 26,817 B | A | view · diff |
| v1.0 | 2026-05-30 | d9b4edd | 23,745 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (28568 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
petrkindlmann/qa-skills · 237 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wahhul5tac4dphk3 GET https://markdownregistry.com/api/v1/resolve?ref=petrkindlmann/qa-skills/release-readiness GET https://markdownregistry.com/api/v1/blob/601a498037d980daa29ec1d6539024b43a35d7c4d9f4d82ecd6d6d2477aff019
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from petrkindlmann/qa-skills
Every file in petrkindlmann/qa-skills