D

Deploy Checklist Command

Generate a comprehensive pre-deployment checklist with automated pre-flight checks, rollback plans, and readiness verification. Prevents deployment disasters by ensuring every critical step is validated before pushing to production.

CommandCommunitydeploymentv1.0.0MIT
0 views0 copies

Command

/deploy-checklist

Description

Generates a deployment-specific checklist by analyzing your current changes, environment configuration, and infrastructure setup. Runs automated checks where possible and flags items requiring manual verification.

Behavior

  1. Analyze the current branch diff against the deploy target
  2. Identify risky changes (database migrations, env vars, breaking APIs)
  3. Run automated pre-flight checks (tests, build, lint)
  4. Generate a customized checklist with rollback procedures
  5. Output a go/no-go summary

Pre-Flight Checks (Automated)

# These run automatically when the command is invoked [ ] git status clean (no uncommitted changes) [ ] All tests passing [ ] Build succeeds [ ] No lint errors [ ] No TypeScript errors [ ] Dependencies up to date (no security advisories) [ ] Environment variables validated

Checklist Template

Pre-Deploy

  • Code Review: All PRs approved and merged
  • Tests: Full test suite passing (unit, integration, e2e)
  • Build: Production build completes without warnings
  • Migrations: Database migrations tested on staging
  • Environment: All new env vars added to production config
  • Dependencies: No known vulnerable packages
  • API Changes: Breaking changes communicated to consumers
  • Feature Flags: New features behind flags if needed

During Deploy

  • Notify Team: Post in #deployments channel
  • Monitor: Watch error rates during rollout
  • Canary: Deploy to canary/staging first if available
  • Health Check: Verify health endpoint returns 200
  • Smoke Test: Hit critical user paths manually

Post-Deploy

  • Monitoring: Check dashboards for anomalies (15 min)
  • Logs: Review error logs for new patterns
  • Performance: Verify response times within SLO
  • Alerts: Confirm monitoring alerts are active
  • Documentation: Update changelog/release notes

Rollback Plan

**Trigger**: Error rate > 5% OR P99 latency > 2s OR critical feature broken **Steps**: 1. Revert deployment: `[platform-specific rollback command]` 2. Verify rollback: Check health endpoint 3. If DB migration was applied: Run `[down migration command]` 4. Notify team in #incidents 5. Create incident report **Estimated rollback time**: ~5 minutes

Output Format

## Deploy Checklist: feature/user-auth -> production **Date**: 2026-03-25 14:30 UTC **Changes**: 12 files, 2 migrations, 1 new env var ### Automated Checks - [x] Tests: 342/342 passing - [x] Build: success (2m 14s) - [x] Lint: 0 errors - [ ] WARN: New env var AUTH_SECRET not found in production config - [ ] WARN: Migration 0042_add_sessions alters users table (high-traffic) ### Risk Assessment: MEDIUM - Database migration on high-traffic table - New authentication flow ### Recommendation: PROCEED WITH CAUTION Deploy during low-traffic window. Monitor closely for 30 minutes.

Examples

# Generate checklist for current branch /deploy-checklist # Specify target environment /deploy-checklist --env production # Include rollback commands for specific platform /deploy-checklist --platform vercel
Community

Reviews

Write a review

No reviews yet. Be the first to review this template!

Similar Templates