deployment

Manages release workflows with deployment strategies, rollback plans, and CI gates.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/rhorba/RestoLedger --skill deployment-rhorba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment
Source: https://github.com/rhorba/RestoLedger/tree/main/skills/deployment
Command: npx skills add https://github.com/rhorba/RestoLedger --skill deployment-rhorba

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Shipping code to production involves risky decisions about deployment strategies, environment configuration, and rollback plans, and a single mistake can cause downtime or data loss. This Skill provides structured checklists, proven deployment patterns, and mandatory CI gates so releases go out safely and can be reversed quickly when something breaks. ## Core Features & Use Cases - Deployment Strategy Selection: Compare rolling, blue-green, canary, recreate, and feature-flag approaches with risk and downtime trade-offs to pick the right one for each release. - Pre-Deployment & Rollback Checklists: Verify code readiness, infrastructure health, SSL/DNS configuration, and rollback procedures before any release goes live. - Ready-to-Use Commands: Execute Docker Compose and Kubernetes deploy and rollback commands, including kubectl rollout undo for instant recovery. - Use Case: You need to ship a new API version to production on Kubernetes. The Skill walks you through confirming CI is green, deploying with kubectl set image, watching the rollout, monitoring error rates for 15 minutes, and rolling back instantly if post-deploy checks fail. ## Quick Start Ask the assistant to prepare a production deployment plan for your application, including a pre-deployment checklist, the right deployment strategy, and a rollback procedure.

Frequently Asked Questions about deployment

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

FAQPage Schema
How do I deploy an application to Kubernetes with zero downtime?

Use a rolling or blue-green deployment strategy. With Kubernetes, run `kubectl set image deployment/app app=registry/app:$TAG` and watch the rollout with `kubectl rollout status`. For critical services, deploy to an idle green environment, smoke test it, then switch traffic.

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

Blue-green deploys the new version to a full idle environment and switches all traffic at once, giving instant rollback by flipping back. Canary releases to a small percentage of instances first (e.g., 5%), compares error rates against baseline, and gradually increases traffic.

How do I rollback a Kubernetes deployment after a failed release?

Run `kubectl rollout undo deployment/app -n production` to return to the previous revision, or add `--to-revision=N` for a specific version. Rollback immediately if the issue affects data integrity, security, more than 5% of users, or turns CI red.

Should I deploy when CI is failing on the target branch?

No. CI must be green before any deployment is permitted, with no exceptions. If CI is red, stop, hand off to DevOps to diagnose, and only resume once the pipeline passes. If CI turns red after a deploy, roll back immediately.

When should I use feature flags instead of a canary deployment?

Use feature flags for gradual rollouts where you want to toggle functionality without redeploying, since rollback is just turning the flag off. Canary deployments suit validating infrastructure-level changes under real traffic with metric comparison.