deploy

---
trigger: /deploy [environment]
title: Deployment Checklist
description: |
  Run a production-ready deployment workflow with pre-checks, build verification,
  environment validation, platform-aware deployment, and post-deploy verification.
  Supports `--dry-run` to check without deploying and `--force` to skip non-critical steps.
parameters:
  - name: environment
    description: Target deployment environment (e.g., staging, production). If omitted, defaults to production.
    required: false
  - name: dry-run
    description: Perform all checks but do not execute the actual deployment.
    type: boolean
    default: false
  - name: force
    description: Skip non-critical checks (e.g., bundle size warnings, minor test failures). Use with caution.
    type: boolean
    default: false
---

Deployment Workflow

Target environment: {{environment | default('production')}}
Dry-run: {{dry-run | default(false)}}
Force mode: {{force | default(false)}}

---

1. Pre-Deploy Checks

• Tests pass: Run the project’s test suite (e.g., npm test, pytest, go test ./...).
  If tests fail and --force is not set → abort. If --force is set → warn and continue.
• No uncommitted changes: git status --porcelain should be empty.
  If dirty → abort (unless --force is set, then stash or warn).
• Branch is up-to-date: git fetch origin && git status -sb shows ahead only if you have local commits you intend to push.
  If behind → abort (merge/rebase first).

2. Build Verification

• Production build succeeds: Run the build command (npm run build, vite build, docker build …, etc.).
  If it fails → abort (even with --force).
• Bundle size within limits: Check the output size of assets.
  If size exceeds project-specific thresholds (e.g., >300 kB gzipped for JS) → warn.
  If --force is set → skip this warning, otherwise prompt for confirmation.
• No new warnings/errors: Review build output for any unexpected warnings.