--- name: deploy description: Produce a deployment checklist plus the Helm, kubectl, and Terraform commands needed to ship a service. Use when deploying or releasing, promoting to staging or production, rolling back, or preparing a change window. argument-hint: "" --- > **Recommended model:** `gpt-5.6-terra`  ·  **Agent mode:** `ask` > > Skills are portable across agent clients, so they carry no Copilot-specific > `model:` field. Set the model via the picker, a custom agent, or the > slot mapping in `.github/model-compatibility.json`. Read the active file to identify: service name, version/image tag, and target environment. Then produce the following — fill all `` from the file context: ## 1. Pre-flight checklist - [ ] All CI checks green on the release branch - [ ] Docker image `/:` exists in Artifactory - [ ] `values-.yaml` reviewed — resource limits and replica count correct - [ ] Secrets rotated if this release touches authentication or credentials - [ ] DB migrations tested against a staging database snapshot (if applicable) - [ ] On-call engineer notified in #deployments Slack channel ## 2. Dry run (always run this first) ```bash helm diff upgrade charts/ \ --namespace \ --values charts//values-.yaml \ --set image.tag= ``` Review the diff carefully. Stop if any `-/+` (destroy + recreate) lines appear. ## 3. Live deploy ```bash helm upgrade --install charts/ \ --namespace \ --values charts//values-.yaml \ --set image.tag= \ --atomic \ --timeout 5m \ --history-max 5 ``` `--atomic` rolls back automatically if health checks fail within 5 minutes. ## 4. Smoke test ```bash kubectl rollout status deployment/ -n --timeout=3m kubectl logs -l app= -n --tail=50 curl -sf https:///actuator/health | jq .status ``` ## 5. Rollback (if needed) ```bash helm history -n # list revisions helm rollback 0 -n # 0 = previous revision ``` ## 6. Post-deploy - [ ] Error rate and p99 latency unchanged in Datadog - [ ] Alert rules re-enabled if they were silenced - [ ] JIRA ticket moved to Done, #releases updated