deployment

Plan and execute blue-green, canary, rolling, or recreate deployments with rollback workflows.

5|2|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/ZacharyLuz/github-copilot-chat-exporter --skill deployment-zacharyluz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment
Source: https://github.com/ZacharyLuz/github-copilot-chat-exporter/tree/main/.claude/skills/devops/deployment
Command: npx skills add https://github.com/ZacharyLuz/github-copilot-chat-exporter --skill deployment-zacharyluz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deployments are often risky, manual, and error-prone. This Skill provides structured, repeatable deployment strategies to reduce downtime and rollback risk, enabling teams to automate and standardize releases.

Core Features & Use Cases

  • Blue-Green Deployment: implement parallel environments and instant switchover.
  • Canary Deployment: gradual rollout to mitigate risk and validate changes.
  • Rolling Deployment: update instances progressively with health checks.
  • Recreate Deployment: simple, reliable deployment with controlled downtime when acceptable.
  • Feature Flags / Dark Launches: decouple deploy from release and enable gradual exposure.

Quick Start

Start with a staged rollout plan in your CI/CD pipeline. Define a primary deployment strategy (e.g., rolling or blue-green), enable health checks and readiness probes, and implement a small canary release in staging before broader production rollout.

Frequently Asked Questions about deployment

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

FAQPage Schema
How do I achieve zero-downtime deployment for a production application?

Zero-downtime deployment is achieved by using structured rollout strategies like blue-green or canary deployments to progressively shift traffic while running health checks and readiness probes on new instances.

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

Blue-green deployment runs two parallel environments for instant traffic switchover, whereas canary deployment gradually rolls out changes to a subset of users to validate stability before broader production release.

How do I implement an automated rollback procedure when health checks fail?

Automated rollback procedures are implemented by defining rollback workflows in your CI/CD pipeline that trigger when health checks or readiness probes fail, reverting traffic to the previous stable environment.

When should I use feature flags and dark launches instead of a rolling deployment?

Use feature flags and dark launches when you need to decouple deployment from release, allowing you to deploy code safely to production and enable gradual feature exposure without a full environment rollout.

Can I use a recreate deployment strategy if controlled downtime is acceptable?

Yes, recreate deployment is a simple and reliable strategy that fully replaces the old environment with the new version, providing controlled downtime when application availability is not strictly required.