What problem does it solve? Deploying a release involves many error-prone manual steps: merging PRs, waiting for CI, detecting the hosting platform, triggering the deploy, and verifying the site is healthy. This Skill automates that entire post-release workflow while enforcing safety rules against force pushes and unverified rollbacks. ## Core Features & Use Cases - Platform Auto-Detection: Detects Vercel, Fly.io, Netlify, Railway, Render, or GitHub Actions from project config files and uses the right CLI commands. - PR Merge and CI Gating: Reads ship state from memory/last-ship.json, merges the release PR after confirmation, and waits for CI to pass before deploying. - Health Checks and Rollback: Runs HTTP health checks with retries after deploy and presents rollback commands on failure without auto-executing them. - Use Case: After running a release with zuvo:ship, invoke this Skill to push the release branch, merge PR #42, wait for GitHub Actions, deploy to Vercel, and verify https://myapp.com returns HTTP 200. ## Quick Start Deploy the current release to production and verify the health of my production URL.