deploy

Deploy releases to production platforms and verify health with rollback options.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill deploy-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/greglas75/zuvo/tree/main/skills/deploy
Command: npx skills add https://github.com/greglas75/zuvo --skill deploy-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy to production after creating a release?

Run the deploy Skill after zuvo:ship has recorded state in memory/last-ship.json. It pushes the release branch and tag, merges the PR if applicable, waits for CI, detects your platform, deploys, and runs a health check.

How to deploy to Vercel, Fly.io, or Netlify automatically?

The Skill detects your platform from config files like vercel.json, fly.toml, or netlify.toml, then runs the matching CLI command such as vercel --prod or fly deploy. If no CLI is available, it falls back to webhook or manual instructions.

Can I deploy without waiting for CI checks?

Yes, pass the --skip-ci-wait flag to bypass the CI polling phase. You can also skip the post-deploy health check with --skip-health, though both are recommended for safe releases.

What happens if the health check fails after deployment?

The Skill retries the health check up to 3 times, then reports FAIL and prints the platform-specific rollback command. It never auto-executes a rollback; you decide whether to run it.

Does the deploy Skill work without GitHub CLI?

Partially. Without gh, PR merge and CI checks are skipped with manual instructions printed, and the verdict is set to PARTIAL. Direct-flow deploys can still proceed with manual CI verification.

Why does deploy refuse to push my release branch?

The Skill validates that the branch and tag still point at the exact commit ship gated, and that the remote matches the recorded pushRemote. If refs moved or memory/last-ship.json is missing, it stops to prevent deploying ungated code.