deployment-checklist-generator — Claude Code skill
deployment-checklist-generator generates deployment runbooks, pre-release checklists, smoke-test scripts, and post-launch verification plans.
MIT 264 installs ★ 64 updated 2026-01-12
npx skills add patricio0312rev/skills --skill deployment-checklist-generator -a claude-codeWhat deployment-checklist-generator does
This skill supplies structured checklists covering pre-flight checks, infrastructure readiness, rollback plans, and stakeholder notifications. It splits verification into stages, from code review confirmations to post-release metric monitoring.
Inside, you will find markdown templates for team reviews, a multi-step GitHub Actions workflow featuring pre-deploy gates, and a standalone bash script for staging or production smoke testing.
Running the included bash test suite requires curl and jq installed in your test runtime.
What it helps with
- draft pre-deployment inspection checklists for team sign-off
- write automated bash smoke tests for endpoints and databases
- build a GitHub Actions deploy job with approval gates
- structure post-release health verification checklists
Example prompts for the agent
- Create a production deployment checklist for our upcoming release
- Generate a smoke test script to verify login and critical API endpoints
- Draft a post-deployment verification runbook for the ops team
How to install deployment-checklist-generator
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill deployment-checklist-generator -a claude-code2Manually: put the files in place
~/.claude/skills/deployment-checklist-generator/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/deployment-checklist-generator/
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill deployment-checklist-generator -a codex2Manually: put the files in place
.agents/skills/deployment-checklist-generator/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill deployment-checklist-generator -a cursor2Manually: put the files in place
.cursor/skills/deployment-checklist-generator/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install patricio0312rev/skills ci-cd/deployment-checklist-generator/SKILL.md2Manually: put the files in place
.github/skills/deployment-checklist-generator/SKILL.md1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill deployment-checklist-generator -a gemini-cli2Platform CLI
gemini skills install https://github.com/patricio0312rev/skills --path ci-cd/deployment-checklist-generatorManually: put the files in place
.devin/skills/deployment-checklist-generator/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill deployment-checklist-generator -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about deployment-checklist-generator
How to install deployment-checklist-generator in Claude Code?
Run npx skills add patricio0312rev/skills --skill deployment-checklist-generator -a claude-code in your terminal to save the skill to ~/.claude/skills/deployment-checklist-generator/SKILL.md.
What does deployment-checklist-generator do?
It gives conversational AI agents structured templates for deployment runbooks, CI/CD safety checks, manual approval workflows, and smoke verification.
What tools are needed to execute the smoke test script?
The generated bash script requires curl for HTTP requests and jq for parsing JSON auth tokens.
Source text
SKILL.md · MIT
---
name: deployment-checklist-generator
description: Creates comprehensive deployment checklists with pre-deployment checks, smoke tests, verification steps, and sign-off workflows. Use for "deployment checklist", "release verification", "deployment runbook", or "production readiness".
---
# Deployment Checklist Generator
Ensure safe, reliable deployments with comprehensive checklists.
## Pre-Deployment Checklist
```markdown
# Pre-Deployment Checklist
## Code Quality
- [ ] All CI checks passing
- [ ] Code review approved (2+ reviewers)
- [ ] No known critical bugs
- [ ] Security scan passed
- [ ] Performance tests passed
## Dependencies
- [ ] All dependencies up to date
- [ ] No high/critical vulnerabilities
- [ ] Bundle size within budget
- [ ] Third-party services operational
## Database
- [ ] Migrations tested in staging
- [ ] Backup completed
- [ ] Rollback plan documented
- [ ] Data migration scripts reviewed
## Infrastructure
- [ ] Servers have capacity
- [ ] CDN cache invalidation plan
- [ ] Load balancer configured
- [ ] SSL certificates valid
## Documentation
- [ ] Changelog updated
- [ ] API docs updated (if changed)
- [ ] Deployment notes prepared
- [ ] Rollback instructions ready
## Communication
- [ ] Stakeholders notified
- [ ] Maintenance window scheduled (if needed)
- [ ] Support team briefed
- [ ] Status page prepared
## Deployment Window
- [ ] Off-peak hours selected
- [ ] Team available for monitoring
- [ ] Emergency contacts confirmed
```
## Deployment Workflow with Checks
```yaml
# .github/workflows/deploy.yml
name: Deploy to Production
on:
workflow_dispatch:
jobs:
pre-deploy-checks:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Check branch
run: |
if [ "${{ github.ref }}" != "refs/heads/main" ]; then
echo "❌ Can only deploy from main branch"
exit 1
fi
- name: Verify CI passed
uses: actions/github-script@v7
with:
script: |
const checks = await github.rest.checks.listForRef({
owner: context.repo.owner,
repo: context.repo.repo,
ref: context.sha,
});
const failed = checks.data.check_runs.filter(
check => check.conclusion === 'failure'
);
if (failed.length > 0) {
throw new Error(`CI checks failed: ${failed.map(c => c.name).join(', ')}`);
}
- name: Check deployment window
run: |
HOUR=$(date +%H)
if [ $HOUR -ge 9 ] && [ $HOUR -le 17 ]; then
echo "⚠️ Deploying during business hours"
else
echo "✅ Deploying outside business hours"
fi
- name: Verify staging deployment
run: |
if ! curl -f https://staging.myapp.com/health; then
echo "❌ Staging is not healthy"
exit 1
fi
deploy:
needs: pre-deploy-checks
runs-on: ubuntu-latest
environment:
name: production
url: https://myapp.com
steps:
- uses: actions/checkout@v4
- name: Backup database
run: ./scripts/backup-db.sh
- name: Deploy
run: ./scripts/deploy.sh production
- name: Run smoke tests
run: ./scripts/smoke-tests.sh production
- name: Update status page
run: |
curl -X POST https://statuspage.io/api/v1/incidents \
-H "Authorization: Bearer ${{ secrets.STATUSPAGE_TOKEN }}" \
-d '{"name":"Deployment Complete","status":"resolved"}'
- name: Create deployment record
uses: actions/github-script@v7
with:
script: |
github.rest.repos.createDeployment({
owner: context.repo.owner,
repo: context.repo.repo,
ref: context.sha,
environment: 'production',
description: 'Production deployment',
});
```
## Smoke Test Script
```bash
#!/bin/bash
# scripts/smoke-tests.sh
ENVIRONMENT=$1
BASE_URL="https://${ENVIRONMENT}.myapp.com"
echo "🔍 Running smoke tests for $ENVIRONMENT..."
FAILED=0
# Test 1: Health endpoint
echo "Test 1: Health check"
if curl -f "$BASE_URL/health" | grep -q "ok"; then
echo "✅ Health check passed"
else
echo "❌ Health check failed"
FAILED=1
fi
# Test 2: User authentication
echo "Test 2: User login"
TOKEN=$(curl -s -X POST "$BASE_URL/api/auth/login" \
-H "Content-Type: application/json" \
-d '{"email":"[email protected]","password":"test123"}' \
| jq -r '.token')
if [ -n "$TOKEN" ] && [ "$TOKEN" != "null" ]; then
echo "✅ Login passed"
else
echo "❌ Login failed"
FAILED=1
fi
# Test 3: Critical API endpoints
echo "Test 3: API endpoints"
ENDPOINTS=("/api/users" "/api/products" "/api/orders")
for endpoint in "${ENDPOINTS[@]}"; do
STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $TOKEN" \
"$BASE_URL$endpoint")
if [ "$STATUS" == "200" ]; then
echo "✅ $endpoint: $STATUS"
else
echo "❌ $endpoint: $STATUS"
FAILED=1
fi
done
# Test 4: Database connectivity
echo "Test 4: Database check"
if curl -f "$BASE_URL/api/health/db" | grep -q "connected"; then
echo "✅ Database connected"
else
echo "❌ Database connection failed"
FAILED=1
fi
# Test 5: External services
echo "Test 5: External services"
SERVICES=("stripe" "sendgrid" "aws")
for service in "${SERVICES[@]}"; do
if curl -f "$BASE_URL/api/health/$service" | grep -q "ok"; then
echo "✅ $service: connected"
else
echo "❌ $service: connection failed"
FAILED=1
fi
done
if [ $FAILED -eq 1 ]; then
echo "❌ Smoke tests failed"
exit 1
fi
echo "✅ All smoke tests passed"
exit 0
```
## Post-Deployment Verification
```markdown
# Post-Deployment Verification
## Immediate Checks (0-5 minutes)
- [ ] Deployment completed successfully
- [ ] All smoke tests passed
- [ ] Health checks returning 200
- [ ] No 5xx errors in logs
- [ ] Application responding
## Short-term Monitoring (5-30 minutes)
- [ ] Error rate <1%
- [ ] Response time p95 <500ms
- [ ] CPU usage normal (<70%)
- [ ] Memory usage stable
- [ ] Database queries performing well
## Feature Verification
- [ ] Login/authentication working
- [ ] Checkout flow functional
- [ ] Search returning results
- [ ] Email notifications sending
- [ ] Payment processing working
## Metrics Dashboard
- [ ] Request volume normal
- [ ] Success rate >99%
- [ ] Latency within SLA
- [ ] No spike in errors
- [ ] User engagement stable
## Long-term Monitoring (1-24 hours)
- [ ] No user complaints
- [ ] Support tickets normal
- [ ] Revenue tracking normal
- [ ] All scheduled jobs running
- [ ] No memory leaks detected
```
## Sign-off Template
```yaml
- name: Request deployment approval
uses: trstringer/manual-approval@v1
with:
secret: ${{ secrets.GITHUB_TOKEN }}
approvers: tech-lead,ops-manager
minimum-approvals: 2
issue-title: "Approve Production Deployment"
issue-body: |
## Deployment Details
**Version:** ${{ github.ref_name }}
**Commit:** ${{ github.sha }}
**Changes:** See [changelog](CHANGELOG.md)
## Pre-deployment Checklist
- ✅ All CI checks passed
- ✅ Code review completed
- ✅ Security scan passed
- ✅ Staging verified
## Approval Required
This deployment requires approval from tech lead and ops manager.
**Approve:** Comment "approve" or "lgtm"
**Reject:** Comment "reject" or "block"
```
## Monitoring Dashboard
```markdown
# Deployment Monitoring Dashboard
## Key Metrics
### Health
- API Health: ✅ UP
- Database: ✅ Connected
- Cache: ✅ Connected
### Performance
- Requests/min: 1,234
- Error rate: 0.2%
- p50 latency: 120ms
- p95 latency: 450ms
- p99 latency: 1,200ms
### Infrastructure
- CPU: 45%
- Memory: 62%
- Disk: 38%
### Business Metrics
- Active users: 523
- Successful checkouts: 89/hour
- Revenue: $15,234/hour
## Alerts
No active alerts
## Recent Deployments
- v1.3.0: Deployed 5 minutes ago ✅
- v1.2.9: Deployed 2 days ago ✅
- v1.2.8: Rolled back 3 days ago ⚠️
```
## Best Practices
1. **Automated checks**: Enforce via CI/CD
2. **Manual review**: Critical deployments need approval
3. **Smoke tests**: Verify key functionality
4. **Gradual rollout**: Canary or blue-green
5. **Monitoring**: Watch metrics for 30 minutes
6. **Communication**: Keep stakeholders informed
7. **Rollback ready**: One-click rollback available
## Output Checklist
- [ ] Pre-deployment checklist
- [ ] Deployment workflow with gates
- [ ] Smoke test script
- [ ] Post-deployment verification
- [ ] Sign-off workflow
- [ ] Monitoring dashboard
- [ ] Communication templates
- [ ] Rollback instructions
© patricio0312rev · MIT · patricio0312rev/skills