deploy-checklist
/deploy-checklist
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.
- Author
- charlieviettq ↗
- Repository
- awesome-agent-skill ↗
- Licence
- MIT
- Last repository change
- 20.07.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 20.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Arguments
/deploy-checklist [service or release name]
Original author 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.
How it works
- Usage
- Output
- Customization
- If Connectors Available
- Tips
SKILL.md preview
--- name: deploy-checklist version: 1 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. argument-hint: [service or release name] triggers: - "deploy-checklist" - "/deploy-checklist" - "[service or release name]" - "pre-deployment" - "verification" - "checklist" tools: [] mutating: false priority: normal source: "anthropics/knowledge-work-plugins/engineering" --- # /deploy-checklist > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS-engineering.md). Generate a pre-deployment checklist to verify readiness before shipping. ## Usage ``` /deploy-checklist $ARGUMENTS ``` ## Output ```markdown ## 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] fails ``` ## 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.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · charlieviettq/awesome-agent-skill | 100 | MIT |
| anthropics/knowledge-work-plugins | 100 | Apache-2.0 |
Identical content appears in 3 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 9286a81dcc48 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100release-checklist
Build a release checklist and go/no-go plan covering semantic versioning, changelog, green CI and security gates, signed artifacts, database migrations, feature flags, staged rollout and a tested rollback plan. Use when the user is preparing a release or deploy, cutting a tag,… - 100deployment-checklist
Run pre-deployment verification before pushing to staging or production — build, tests, env config, security, DB, infra, integration — and return a READY / NOT READY verdict. Trigger on: "pre-deploy check", "deployment checklist", "ready to ship", "is this ready for prod",… - 100perplexity-prod-checklist
Execute Perplexity production deployment checklist and rollback procedures. Use when deploying Perplexity integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "perplexity production", "deploy perplexity", "perplexity… - 100hex-prod-checklist
Execute Hex production deployment checklist and rollback procedures. Use when deploying Hex integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "hex production", "deploy hex", "hex go-live", "hex launch checklist". - 100ship
Get a change safely to production: CI quality gates, a pre-release checklist, rollback plan, logs, metrics and alerts for the new behavior, and a PR that shows evidence and merge risk. Use when setting up CI, preparing a release, or opening a PR. - 100firecrawl-prod-checklist
Execute FireCrawl production deployment checklist and rollback procedures. Use when deploying FireCrawl integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "firecrawl production", "deploy firecrawl", "firecrawl…