deploy-production

Orchestrate production deployments with approval gates and automated rollbacks.

2|Updated Mar 19, 2026

Search Tags:#devops #deployment #production #safety #kubernetes #sre

Ready to run

npx skills add https://github.com/alex-voloshin-dev/ai-skills --skill deploy-production-alex-voloshin-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploy-production
Source: https://github.com/alex-voloshin-dev/ai-skills/tree/main/.windsurf/skills/deploy-production
Command: npx skills add https://github.com/alex-voloshin-dev/ai-skills --skill deploy-production-alex-voloshin-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill mitigates the risk of human error and service downtime during production releases by enforcing mandatory approval gates, verification steps, and structured rollback procedures.

Core Features & Use Cases

Approval Gates: Ensures no production mutation occurs without explicit user authorization.
Verification & Rollback: Provides a standardized checklist for pre-deployment readiness, post-deployment health checks, and automated rollback commands.
Use Case: A DevOps engineer uses this skill to safely roll out a new microservice version, ensuring that database migrations are verified and that the system can be reverted instantly if health checks fail.

Quick Start

Initiate the production deployment process for the specified service and version by following the guided checklist and requesting approval for each mutation step.

Frequently Asked Questions about deploy-production

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

FAQPage Schema

How do I enforce mandatory approval gates for Kubernetes production deployments?▼

To enforce mandatory approval gates for Kubernetes production deployments, this skill orchestrates releases by halting execution until explicit user authorization is granted for any service mutation. It ensures no infrastructure changes occur without direct human approval.

What is the best way to automate health checks and rollbacks during a Helm release?▼

The best way to automate health checks and rollbacks during a Helm release is to use a systematic verification protocol that validates post-deployment metrics against monitoring tools. This skill executes automated rollback commands instantly if those health checks fail.

Can I use this deployment skill with my existing CI/CD pipelines and serverless architectures?▼

Yes, you can use this deployment skill with existing CI/CD pipelines and serverless architectures. It applies to cloud-native environments and requires integration with your current monitoring tools to validate health metrics effectively.

How do I verify database migrations before a production rollout?▼

To verify database migrations before a production rollout, follow a guided pre-deployment readiness checklist. This skill provides standardized verification steps to confirm migrations and system stability prior to authorizing the final production release.

Why do I need a structured rollback procedure for microservice deployments?▼

You need a structured rollback procedure for microservice deployments to mitigate the risk of human error and service downtime during high-stakes releases. It ensures the system can be reverted instantly if post-deployment health checks detect failures.