deployment-checklist SKILL.md skillA
deployment-checklist from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qa-aman/claude-skills/deployment-checklist@git:20260303.ca0168fPins git:20260303.ca0168f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qa-aman/claude-skills
- Path
skills/by-role/devops/deployment-checklist/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260303.ca0168f, committed Mar 3, 2026
- Size
- 4,883 bytes
- Repository stars
- 21
- License
- MIT
Run a pre and post-deployment checklist. Use when the user says "deploy to production", "deployment checklist", "release checklist", "pre-deploy checks", "is this ready to deploy", "deployment readiness", "reduce deployment risk", "change management", or is about to ship code to production and wants to reduce failure risk - even if they don't explicitly say "deployment checklist".
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
## Overview Based on **"The Checklist Manifesto"** by Atul Gawande and **"Accelerate"** by Forsgren, Humble & Kim. Gawande's insight: checklists don't exist because people are stupid - they exist because complex, high-pressure situations cause smart people to skip steps they know matter. A pre-deployment checklist is not bureaucracy; it's the discipline that separates teams with 15% change failure rates from teams with 60%. Accelerate's finding: high-performing teams deploy more frequently AND have lower failure rates. The checklist is what enables speed without sacrificing safety. ## Workflow ### Pre-Deployment Checklist Run before every production deployment: **Code and testing:** - [ ] CI pipeline is green (all tests pass, no warnings suppressed) - [ ] Code reviewed and approved by at least one other engineer - [ ] No `TODO: fix before deploy` comments in the diff - [ ] No hardcoded credentials, secrets, or API keys introduced - [ ] Database migrations are backward-compatible (old code can run against new schema) **Deployment mechanics:** - [ ] Deployment plan documented: what is being deployed, to which environment, in what order …
Read the whole file at its exact version.
How to install
mdr add qa-aman/claude-skills/deployment-checklist@sha256:cbc5caae151031b7The line at the top of this page pins the label git:20260303.ca0168f, 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_q3peelterjvb2thn)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 3, 2026.
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 (4883 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
qa-aman/claude-skills · 21 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_q3peelterjvb2thn GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/deployment-checklist GET https://markdownregistry.com/api/v1/blob/cbc5caae151031b7b313766f03f6da2dc17c3a336f10fd9b398398775f3f29ae
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.