Land and Deploy Checklist
By shadow_banned · Published · Updated
Walks a merged change through to production safely: merge, wait for CI and deploy, check live health, and roll back at the first bad signal.
Prompt template
## Land and Deploy Checklist Take an approved pull request live and confirm it is healthy. - Pull request: [text: Link or number] - Merge method: [dropdown: Squash, Merge commit, Rebase] - Deploy pipeline: [text: e.g. GitHub Actions to Cloud Run] - Health signals: [textarea: Endpoints and dashboards and error rates to check] - Rollback method: [textarea: Command or button to revert] - Deploy window: [dropdown: Anytime, Business hours only, Off-peak only] Confirm before merging that approvals are in, checks are green, and the deploy window allows it. Merge with the chosen method, then watch CI and the deploy to completion instead of assuming success. After the deploy, verify production: the version served matches the merge, key endpoints return healthy responses, and error rate and latency sit near their pre-deploy levels over at least ten minutes. Define rollback triggers in advance: error rate above its baseline by a set margin, a failing health endpoint, or a broken core user flow. If any trigger fires, roll back first and investigate second. Report merge time, deploy time, checks passed, any anomaly, and a final status of Healthy, Rolled back, or Needs attention.