deploy

Name: deploy
Availability: InStock
Author: sonhaicoder

Automate production deployment with migration-first, zero-downtime rollout protocol.

Updated May 5, 2026

Search Tags:#deployment #rollback #migration #vercel #zero-downtime #railway #health-check

Ready to run

npx skills add https://github.com/sonhaicoder/haiclaudeskill --skill deploy-sonhaicoder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/sonhaicoder/haiclaudeskill/tree/main/skills/deploy
Command: npx skills add https://github.com/sonhaicoder/haiclaudeskill --skill deploy-sonhaicoder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes and automates production deployments, ensuring migrations run first, health checks pass, and rollbacks are ready, reducing risky manual handoffs.

Core Features & Use Cases

Migration-first rollout ensures DB migrations run before app deploy.
Pre-deploy health checks verify readiness across services (backend, DB, Redis) before routing traffic.
Guardrails for environment management enforce safe secrets handling, port usage, and production configurations.
Rollback preparedness provides quick redeploy to a known-good version with minimal downtime.
Use case: When pushing to main, a three-gate deployment is executed (local build → env check → migration) with health checks prior to traffic cutover.

Quick Start

Use the Deploy Skill to trigger a production rollout when readiness criteria are confirmed.

Frequently Asked Questions about deploy

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

FAQPage Schema

How do I achieve zero-downtime production deployment on Railway or Vercel?▼

Zero-downtime production deployment is achieved by enforcing a migration-first rollout protocol with pre-deploy health checks and multi-stage gates before traffic cutover. This ensures backend services are fully ready before routing traffic.

What is a migration-first rollout strategy and why is it needed?▼

A migration-first rollout strategy ensures database migrations run before the application deploy begins. This sequence prevents application crashes by guaranteeing the new code expects a database schema that has already been updated and ready.

How do I handle environment variables and port configuration for a production rollout?▼

Environment variables and port configuration are handled through deployment guardrails that enforce safe secrets handling and correct port usage. This verifies production configurations across multi-stage gates before routing traffic.

Can I automate rollback procedures if my production deployment fails health checks?▼

Rollback procedures are automated to quickly redeploy to a known-good version with minimal downtime. If pre-deploy health checks fail, the system uses prepared rollback strategies to restore service safely.

What steps are involved in a multi-stage deployment gate workflow?▼

A multi-stage deployment gate workflow executes a three-gate sequence: local build, environment check, and database migration. Pre-deploy health checks verify backend, DB, and Redis readiness before final traffic cutover.