
deploy-checklist
โ Officialโ 22,378by anthropic ยท part of anthropics/knowledge-work-plugins
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.
This is the playbook your agent receives when the skill activates โ you don't need to read it to use the skill, but it's here to audit before installing.
/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.
Output
## Customization
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
1. **Run before every deploy** โ Even routine ones. Checklists prevent "I forgot to..."
2. **Customize once, reuse** โ Tell me your stack and I'll remember your deploy process.
3. **Include rollback criteria** โ Decide when to roll back before you deploy, not during.npx skills add anthropics/knowledge-work-plugins --skill "deploy-checklist" --full-depthRun this in your project โ your agent picks the skill up automatically.
Usage
/deploy-checklist $ARGUMENTSDeploy 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] fails
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.
Licensed under Apache-2.0โ you can use, modify, and redistribute it under that license's terms.
View the full license file on GitHub โ