deployment-patterns

Implements CI/CD pipelines, Docker builds, health checks, and rollback strategies for web application deployments.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/prabaljainn/my-claude-code-setup --skill deployment-patterns-prabaljainn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deployment-patterns
Source: https://github.com/prabaljainn/my-claude-code-setup/tree/main/claude/skills/deployment-patterns
Command: npx skills add https://github.com/prabaljainn/my-claude-code-setup --skill deployment-patterns-prabaljainn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up deployment infrastructure involves many decisions—choosing a deployment strategy, writing Dockerfiles, configuring CI/CD pipelines, and verifying production readiness—and mistakes here cause downtime and failed releases. This Skill provides proven patterns and ready-to-adapt templates for each of these concerns. ## Core Features & Use Cases - Deployment Strategies: Guidance on rolling, blue-green, and canary deployments with trade-offs and traffic diagrams for each approach. - Docker & CI/CD Templates: Multi-stage Dockerfiles for Node.js, Go, and Python/Django, plus a GitHub Actions pipeline covering test, build, and deploy stages. - Production Readiness: Health check endpoints, Kubernetes probe configurations, environment validation with zod, rollback procedures, and a full pre-release checklist. - Use Case: When preparing a Node.js service for its first production release, use this Skill to generate a multi-stage Dockerfile, wire up a GitHub Actions pipeline, add health endpoints, and walk the production readiness checklist before going live. ## Quick Start Ask the AI to help you dockerize your application and set up a CI/CD pipeline with health checks and a rollback plan for production deployment.

Frequently Asked Questions about deployment-patterns

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

FAQPage Schema
How do I set up a CI/CD pipeline with GitHub Actions?▼

Define sequential jobs for test, build, and deploy in a workflow YAML file triggered on pushes to main. The test job runs lint, typecheck, and tests; the build job pushes a Docker image to a registry; the deploy job releases to production only after prior stages pass.

What is the difference between blue-green and canary deployment?▼

Blue-green deployment runs two identical environments and switches all traffic atomically, enabling instant rollback but requiring double infrastructure. Canary deployment routes a small traffic percentage to the new version first, catching issues with real traffic before full rollout.

How do I write a multi-stage Dockerfile for Node.js?▼

Use separate stages for dependency installation, building, and the production runtime. Copy only production node_modules and build output into the final stage, run as a non-root user, pin a specific base image tag like node:22-alpine, and add a HEALTHCHECK instruction.

Does Kubernetes need both liveness and readiness probes?▼

Yes, they serve different purposes. Liveness probes restart containers that are stuck, while readiness probes control whether a pod receives traffic. A startup probe is also recommended for slow-starting applications to avoid premature liveness failures.

When should I not use a rolling deployment?▼

Avoid rolling deployments when changes are not backward-compatible, since old and new versions run simultaneously during rollout. Use blue-green deployment for critical services needing instant rollback, or canary deployment for risky changes on high-traffic services.