Blue Green Deployment

This handles the infrastructure setup for running two identical production environments and switching traffic between them, typically through load balancers or DNS. You'd reach for this when you need true zero-downtime deployments or want instant rollback without redeploying anything. The skill includes scripts for traffic switching with AWS ALB target groups and rollback automation. It's overkill for simple apps but makes sense for high-stakes releases where you need that safety net of keeping the old environment warm and ready. The main trade-off is running double the infrastructure during deployments, which can get expensive if your transition windows are long.

skills.sh installs: 437
GitHub stars: 379
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aj-geddes/useful-ai-prompts --skill blue-green-deployment --agent claude-code

Installs into .claude/skills of the current project.

Files

Overview

Deploy applications using blue-green deployment patterns to maintain two identical production environments, enabling instant traffic switching and rapid rollback capabilities.

When to Use

Zero-downtime releases
High-risk deployments
Complex application migrations
Database schema changes
Rapid rollback requirements
A/B testing with environment separation
Staged rollout strategies

Quick Start

Minimal working example:

# blue-green-setup.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: blue-green-config
  namespace: production
data:
  switch-traffic.sh: |
    #!/bin/bash
    set -euo pipefail

    CURRENT_ACTIVE="${1:-blue}"
    TARGET="${2:-green}"
    ALB_ARN="arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer/app/myapp-alb/1234567890abcdef"

    echo "Switching traffic from $CURRENT_ACTIVE to $TARGET..."

SKILL.md on GitHub