deployment-patterns

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

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill deployment-patterns-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment-patterns
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/deployment-patterns
Command: npx skills add https://github.com/ibytechaos/claude --skill deployment-patterns-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping web applications to production involves many failure-prone decisions: choosing a deployment strategy, writing efficient Dockerfiles, wiring CI/CD pipelines, and verifying readiness. This Skill provides concrete, copy-ready patterns for each of these steps so teams avoid common production mistakes. ## Core Features & Use Cases - Deployment Strategies: Guidance and diagrams for rolling, blue-green, and canary deployments, including trade-offs and when to use each. - 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 liveness/readiness/startup probes, 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, a GitHub Actions workflow, health check endpoints, and a rollback plan in one pass. ## Quick Start Ask the assistant to set up a production deployment pipeline with Docker, health checks, and a rollback plan for your web application.

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. Run lint, typecheck, and tests on pull requests, then build and push a Docker image to a registry and deploy only from the main branch.

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

Blue-green runs two identical environments and switches all traffic atomically, enabling instant rollback. Canary 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, and add a HEALTHCHECK instruction.

Does Kubernetes need both liveness and readiness probes?

Yes, they serve different purposes. Liveness probes restart unhealthy containers, while readiness probes control whether a pod receives traffic. A startup probe should also be added for slow-starting applications.

When should I not use a rolling deployment?

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