deployment-patterns

Design production deployment workflows with CI/CD stages, Docker health checks, and Kubernetes probes.

Updated May 4, 2026
One-click install
npx skills add https://github.com/gganbukim1/myskills --skill deployment-patterns-gganbukim1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment-patterns
Source: https://github.com/gganbukim1/myskills/tree/main/deployment-patterns
Command: npx skills add https://github.com/gganbukim1/myskills --skill deployment-patterns-gganbukim1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you reduce downtime and production risk by standardizing deployment workflows, CI/CD stages, health checks, rollback plans, and production readiness practices for web applications.

Core Features & Use Cases

  • Deployment Strategy Selection: Compare and apply rolling, blue-green, and canary rollouts based on risk tolerance and infrastructure constraints.
  • Production-Ready CI/CD Pipelines: Define GitHub Actions workflows for test, build, containerize, and deploy stages tied to main-branch releases.
  • Health Checks & Readiness: Implement application health endpoints and Kubernetes liveness/readiness/startup probes to prevent bad traffic and detect degraded behavior.
  • Rollback & Release Readiness: Provide rollback commands and checklists for artifacts, migrations, monitoring, feature flags, and operational readiness.

Quick Start

Use the deployment-patterns skill to generate a deployment plan that includes rolling, blue-green, or canary strategy, a health check design, and a rollback checklist tailored to 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 set up a Kubernetes deployment with health checks and rollback?

Kubernetes deployment with health checks requires configuring liveness, readiness, and startup probes alongside a defined rollback strategy, which this workflow provides by generating rolling, blue-green, or canary rollout plans with matching probe configurations.

What is the best way to configure Docker HEALTHCHECK and CI/CD pipelines for web application releases?

Docker HEALTHCHECK and CI/CD pipelines for web releases are configured by defining GitHub Actions stages for test, build, containerize, and deploy, integrated with Docker best practices to ensure automated, production-ready delivery tied to main-branch commits.

When should I use blue-green versus canary deployment strategies?

Blue-green versus canary deployment strategies depend on your risk tolerance and infrastructure constraints; blue-green offers instant traffic switching while canary gradually shifts traffic, allowing you to compare rollout options and select the safest approach.

How do I create a production readiness checklist for application releases?

Production readiness checklists for application releases are created by verifying artifacts, database migrations, monitoring configurations, feature flags, and operational safeguards, ensuring all prerequisites are met before executing a deployment.

Can I use GitHub Actions to automate Docker containerization and deployment?

GitHub Actions can automate Docker containerization and deployment by specifying build and deploy stages within the CI/CD pipeline, ensuring containerized web applications are delivered safely to production environments.