---
name: Deploy Checklist
slug: deploy-checklist
category: DevOps
description: Deploy Checklist verifies CI, env vars, migrations, rollback plans, smoke tests, and monitoring before and after a production deployment. Use it when a change is ready to ship or has just been deployed.
github: "https://github.com/wednesday-solutions/ai-agent-skills/tree/main/skills/deploy-checklist"
language: JavaScript
stars: 168
forks: 21
install: "npx degit https://github.com/wednesday-solutions/ai-agent-skills/tree/main/skills/deploy-checklist ~/.claude/skills/deploy-checklist"
installs_to: ~/.claude/skills/deploy-checklist
source_path: skills/deploy-checklist/SKILL.md
collection_size: 10
category_size: 1075
collection_url: "https://dirskills.com/collections/wednesday-solutions/ai-agent-skills"
added: 2026-09-08T05:34:06.907Z
last_synced: 2026-09-08T05:34:06.907Z
canonical_url: "https://dirskills.com/skills/deploy-checklist"
---

# Deploy Checklist

Deploy Checklist verifies CI, env vars, migrations, rollback plans, smoke tests, and monitoring before and after a production deployment. Use it when a change is ready to ship or has just been deployed.

**Install:**

```bash
npx degit https://github.com/wednesday-solutions/ai-agent-skills/tree/main/skills/deploy-checklist ~/.claude/skills/deploy-checklist
```

## README

# Deploy Checklist Skill

## Trigger

Load this skill when a dev is about to deploy or has just deployed:
- "We're deploying to production"
- "Pre-deploy check"
- "Post-deploy verification"
- "Run the deploy checklist"
- "Is it safe to deploy?"

**Do NOT use this skill for:** committing code (use `git-os`), creating a PR (use `pr-create`), or planning a project (use `greenfield`). This skill only applies at the deployment stage — code is already merged.

---

Run this checklist before and after every production deployment.

## Pre-Deploy Checklist

- [ ] All CI checks green on the deploy branch
- [ ] Environment variables verified in target environment (no missing keys)
- [ ] Database migrations reviewed — irreversible migrations documented
- [ ] Migrations have been dry-run or tested in staging
- [ ] Rollback plan documented: what to revert and how
- [ ] Feature flags set correctly for the release
- [ ] Downstream services notified if API contracts changed
- [ ] Changelog updated with this release's changes
- [ ] Deployment window confirmed (avoid peak traffic)

## Deploy

- [ ] Deploy initiated with correct branch / tag
- [ ] Deployment logs monitored in real time
- [ ] No unexpected errors during startup

## Post-Deploy Checklist

- [ ] Smoke test: critical user flows verified manually or via synthetic monitoring
- [ ] Health check endpoint returns 200
- [ ] Error rate in monitoring (Datadog, Grafana, Sentry) is normal
- [ ] No spike in latency or DB query time
- [ ] Monitoring alerts reviewed — no new alerts triggered
- [ ] Changelog published / communicated to stakeholders
- [ ] Ticket status updated (closed / released)

## Rollback Trigger Criteria

Initiate rollback immediately if:
- Error rate rises above 1% of requests
- P95 latency increases by more than 2x baseline
- Any data integrity issue detected
- Critical feature path returns 5xx

## Tools

| Action | Tool |
|--------|------|
| Run lint, test, build scripts | `Bash` |
| Check health endpoint | `Bash` — `curl -s <url>/health` |
| Read config or env files | `Read` |
| Check CI status | `Bash` — `gh run list` or `gh pr checks` |

## Notes

- Never deploy on Fridays unless it's a critical hotfix
- Always have a second engineer available during production deploys
- Document the actual deploy time and outcome in the ticket