deploy

Orchestrate zero-downtime deployments with health-gated rollouts and automatic rollback.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates risky, manual deployments by designing and orchestrating controlled rollout strategies that minimize user impact, ensure quick recovery from regressions, and coordinate complex changes like database migrations and feature flag releases.

Core Features & Use Cases

  • Strategy selection: Recommends blue-green, canary, progressive, or rolling deployments based on change risk and system constraints.
  • Automated gates & rollback: Defines health-based gates, telemetry thresholds, and automatic rollback triggers to stop and revert harmful changes.
  • Feature flag orchestration: Coordinates staged flag rollouts and kill switches to decouple deploy from release.
  • Zero-downtime migrations: Prescribes expand-contract schema migrations and service strangler patterns for safe data and service transitions.
  • Operational reporting: Produces deployment plans, TSV logs, and post-deploy reports for audit and incident review.

Quick Start

Start a canary deployment for feature checkout-v2 with 5% initial traffic, automated health gates, and automatic rollback if error rate exceeds 1%.

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I ensure zero-downtime during application deployments?

Zero-downtime application deployments are orchestrated using blue-green swaps, canary releases, or progressive traffic shifting with automated health gates and rollback triggers. This eliminates risky manual rollouts and ensures quick recovery from regressions.

What is the best way to automate rollback when error rates spike after a release?

Automate rollback by defining health-based gates and telemetry thresholds that trigger automatic reverts during production rollouts. If error rates exceed defined limits, the deployment stops and automatically reverts harmful changes to maintain system stability.

How do I coordinate database schema migrations without downtime?

Coordinate zero-downtime database schema migrations using expand-contract patterns and service strangler patterns. This prescribes safe data and service transitions, allowing schema changes without locking tables or disrupting active production traffic.

Can I decouple code deployment from feature release using feature flags?

Yes, you can decouple deploy from release by orchestrating staged feature flag rollouts and kill switches. This coordinates traffic shifting and feature availability independently of code deployment, allowing safer progressive exposure.

When should I choose canary releases over blue-green deployments?

Canary releases suit progressive rollouts shifting partial traffic to monitor telemetry, while blue-green deployments swap entire environments for instant rollback. Strategy selection depends on change risk, system constraints, and required traffic shifting granularity.

What are the limitations of progressive rollouts for infrastructure changes?

Progressive rollouts for infrastructure changes require strict health-based gates and telemetry thresholds to function safely. Without automated rollback triggers and expand-contract migration support, complex infrastructure transitions risk failing zero-downtime requirements.