jeremylongshore/tons-of-skills-marketplace / plugins/devops/deployment-rollback-manager/skills/managing-deployment-rollbacks
managing-deployment-rollbacks
VerifiedDeploy use when you need to work with deployment and CI/CD. This skill provides deployment automation and orchestration with comprehensive guidance and automation. Trigger with phrases like "deploy application", "create pipeline", or "automate deployment".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.7 KB |
| assets/README.md | markdown | 342 B |
| assets/example_rollback_config.yml | config | 3.7 KB |
| assets/rollback_report_template.md | markdown | 4.8 KB |
| assets/rollback_template.yml | config | 3.3 KB |
| references/README.md | markdown | 70 B |
| scripts/README.md | markdown | 484 B |
| scripts/get_previous_version.pyexecutable | script | 2.8 KB |
| scripts/rollback_deployment.pyexecutable | script | 5.5 KB |
| scripts/verify_deployment.pyexecutable | script | 5.5 KB |
assets/rollback_template.yml
View on GitHub# rollback_template.yml
# This file defines the configuration for a deployment rollback.
# General Rollback Information
rollback_name: "example-value - Descriptive Rollback Name" # e.g., "Rollback to v1.2.3 due to login issues"
description: "Detailed description of the rollback purpose and context." # More details on why this rollback is necessary.
# Target Environment
environment: "production" # e.g., "staging", "production", "qa"
region: "us-east-1" # AWS region or equivalent
# Deployment Details
application_name: "YOUR_VALUE_HERE - Application Name" # e.g., "web-app", "api-service"
current_version: "YOUR_VALUE_HERE - Current Deployed Version" # e.g., "v1.2.4", "release-2023-10-27"
rollback_version: "YOUR_VALUE_HERE - Version to Rollback To" # e.g., "v1.2.3", "release-2023-10-26"
# Deployment Strategy (Choose one)
deployment_strategy: "blue_green" # Options: "blue_green", "rolling_update", "canary"
# Blue/Green Specific Configuration
blue_green:
active_color: "blue" # e.g., "blue", "green" - Which color is currently serving traffic?
inactive_color: "green" # e.g., "green", "blue" - Which color will be promoted?
switch_traffic_method: "dns_swap" # Options: "dns_swap", "load_balancer_update"
dns_record: "api.example.com" # DNS record to update (if using dns_swap)
load_balancer_arn: "YOUR_VALUE_HERE - ARN of the Load Balancer" # ARN of the load balancer (if using load_balancer_update)
# Rolling Update Specific Configuration
rolling_update:
batch_size: 2 # Number of instances/pods to update in each batch
wait_time: 60 # Seconds to wait between batches for health checks
# Canary Deployment Specific Configuration
canary:
initial_percentage: 10 # Percentage of traffic to route to the canary version initially
increment_percentage: 10 # Percentage to increase traffic to the canary version in each step
increment_interval: 300 # Seconds between traffic increments
max_percentage: 50 # Maximum percentage of traffic to route to the canary version
# Health Check Configuration
health_check:
type: "http" # Options: "http", "tcp", "custom"
url: "/health" # URL to check for HTTP health checks
port: 8080 # Port to check for TCP health checks
timeout: 30 # Seconds before health check times out
success_codes: [200, 204] # HTTP status codes indicating success
interval: 15 # Seconds between health checks
max_failures: 3 # Number of consecutive failures before rollback is considered failed
# Pre-Rollback Checks
pre_rollback_checks:
database_backup: true # Perform a database backup before rollback
monitoring_enabled: true # Ensure monitoring is enabled
alerting_configured: true # Ensure alerting is configured
# Post-Rollback Checks
post_rollback_checks:
health_check_success: true # Verify health checks are passing
performance_metrics_stable: true # Verify performance metrics are within acceptable limits
error_rates_acceptable: true # Verify error rates are within acceptable limits
# Notifications
notifications:
on_success:
- "slack:YOUR_VALUE_HERE - Slack Channel ID" # Send a notification to Slack on success
on_failure:
- "email:YOUR_VALUE_HERE - Email Address" # Send an email on failure
# Advanced Configuration
dry_run: false # Set to true to simulate the rollback without actually executing it
force: false # Set to true to bypass certain safety checks (use with caution)Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |