deploy-checklist
The facts
Its description
Pre-deployment verification checklist. Use when about to ship a release, deploying a change with database migrations or feature flags, verifying CI status and approvals before going to production, or documenting rollback triggers ahead of time.
The description the agent reads to decide when to use it.
When it starts
The agent would pick this skill when the person is getting ready to ship a release or push a change to production and wants a readiness check — especially when the deploy involves database migrations, feature flags, or a need to agree on rollback triggers beforehand. It is triggered by the act of preparing to deploy, not by any other skill.
Things a person might say (the model's guesses)
- “We're shipping the payments service v2.3 tonight, can you put together a deploy checklist?”
- “I'm about to push a change with a database migration and a feature flag — what should I verify first?”
- “Help me document rollback triggers before we go to production.”
A model's summary of when it is used.
What it takes when started
[service or release name]
What to type after its name when you start it.
Licence
Apache-2.0, from LICENSE
The terms its author shares it under, which let it be shown here.
The text
Most marks come from matching words in the file, so treat them as pointers.
/deploy-checklist
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate a pre-deployment checklist to verify readiness before shipping.
Raw lines 1 to 12Boilerplate, lines 13 to 18. The same text appears in 24 other files here. Close
Output
## Deploy Checklist: [Service/Release]
**Date:** [Date] | **Deployer:** [Name]
### Pre-Deploy
- [ ] All tests passing in CI
- [ ] Code reviewed and approved
- [ ] No known critical bugs in release
- [ ] Database migrations tested (if applicable)
- [ ] Feature flags configured (if applicable)
- [ ] Rollback plan documented
- [ ] On-call team notified
### Deploy
- [ ] Deploy to staging and verify
- [ ] Run smoke tests
- [ ] Deploy to production (canary if available)
- [ ] Monitor error rates and latency for 15 min
- [ ] Verify key user flows
### Post-Deploy
- [ ] Confirm metrics are nominal
- [ ] Update release notes / changelog
- [ ] Notify stakeholders
- [ ] Close related tickets
### Rollback Triggers
- Error rate exceeds [X]%
- P50 latency exceeds [X]ms
- [Critical user flow] failsRaw lines 19 to 52Customization
Tell me about your deploy and I'll customize the checklist:
- "We use feature flags" → adds flag verification steps
- "This includes a database migration" → adds migration-specific checks
- "This is a breaking API change" → adds consumer notification steps
If Connectors Available
If ~~source control is connected:
- Pull the release diff and list of changes
- Verify all PRs are approved and merged
If ~~CI/CD is connected:
- Check build and test status automatically
- Verify pipeline is green before deploy
If ~~monitoring is connected:
- Pre-fill rollback trigger thresholds from current baselines
- Set up post-deploy metric watch
Tips
- Run before every deploy — Even routine ones. Checklists prevent "I forgot to..."
- Customize once, reuse — Tell me your stack and I'll remember your deploy process.
- Include rollback criteria — Decide when to roll back before you deploy, not during.
From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.