deployment-patterns

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

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/pjherron/hypoc --skill deployment-patterns-pjherron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deployment-patterns
Source: https://github.com/pjherron/hypoc/tree/main/hypoc/skills/deployment-patterns
Command: npx skills add https://github.com/pjherron/hypoc --skill deployment-patterns-pjherron

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 proven patterns and checklists so deployments are consistent, safe, and reversible. ## Core Features & Use Cases - Deployment Strategies: Guidance and trade-offs for rolling, blue-green, and canary deployments so you can pick the right rollout model. - Docker & CI/CD Templates: Multi-stage Dockerfiles for Node.js, Go, and Python, plus a GitHub Actions pipeline covering test, build, and deploy stages. - Production Readiness: Health check endpoints, Kubernetes probes, environment validation with zod, rollback procedures, and a full pre-release checklist. - Use Case: Before launching a new service, use this Skill to generate a multi-stage Dockerfile, add a /health endpoint with Kubernetes liveness and readiness probes, and walk the production readiness checklist. ## Quick Start Ask the assistant to set up a production deployment pipeline with a multi-stage Dockerfile, health checks, and a rollback plan for your application.

Frequently Asked Questions about deployment-patterns

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

FAQPage Schema
How do I choose between rolling, blue-green, and canary deployments?▼

Rolling deployments suit standard backward-compatible changes with zero downtime. Blue-green fits critical services needing instant rollback but requires double infrastructure. Canary works best for high-traffic services or risky changes, routing a small traffic percentage to the new version first.

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

Use separate stages for dependency installation, build, and production runtime. Copy dependency files first for layer caching, prune dev dependencies, run as a non-root user, pin a specific base image tag like node:22-alpine, and add a HEALTHCHECK instruction.

What should a CI/CD pipeline include before deploying to production?▼

A standard pipeline runs lint, typecheck, unit tests, and integration tests on pull requests. After merge to main, it builds and pushes a tagged Docker image, deploys to staging, runs smoke tests, then promotes to production.

How do Kubernetes liveness and readiness probes differ?▼

Liveness probes detect when a container needs restarting, while readiness probes control whether a pod receives traffic. A startup probe gives slow applications time to boot before the other probes apply, avoiding premature restarts.

How do I roll back a failed production deployment?▼

For Kubernetes, run kubectl rollout undo on the deployment. Vercel and Railway support promoting a previous deployment or commit. Rollback requires that database migrations be backward-compatible and that the previous image artifact remains tagged and available.

Why should environment variables be validated at application startup?▼

Validating configuration at startup with a schema library like zod makes the application fail fast on missing or malformed values instead of crashing later at runtime. It enforces required secrets, correct URL formats, and valid enum values before serving traffic.