Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/devops/deployment-rollback-manager/skills/managing-deployment-rollbacks

managing-deployment-rollbacks

Verified

Deploy 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".

FileKindSize
SKILL.mdskill md4.7 KB
assets/README.mdmarkdown342 B
assets/example_rollback_config.ymlconfig3.7 KB
assets/rollback_report_template.mdmarkdown4.8 KB
assets/rollback_template.ymlconfig3.3 KB
references/README.mdmarkdown70 B
scripts/README.mdmarkdown484 B
scripts/get_previous_version.pyexecutablescript2.8 KB
scripts/rollback_deployment.pyexecutablescript5.5 KB
scripts/verify_deployment.pyexecutablescript5.5 KB

assets/example_rollback_config.yml

View on GitHub
# Configuration file for Deployment Rollback Manager Plugin

# --- General Settings ---
general:
  # Description of this rollback configuration.  Useful for identifying different scenarios.
  description: "Rollback to version 1.2.3 due to critical bug found in 1.2.4"

  # Environment to perform the rollback in.  Should match your deployment environment.
  environment: "production"  # Example: production, staging, dev

  # Whether to automatically approve the rollback after safety checks pass.
  # Set to false for manual approval after checks.
  auto_approve: false

# --- Deployment Settings ---
deployment:
  # Target application or service name.
  application_name: "YOUR_APPLICATION_NAME"

  # Deployment platform to rollback. Options: kubernetes, docker, aws_ecs, manual_script
  platform: "kubernetes"

  # Version to rollback to.
  rollback_version: "1.2.3"

  # Current version being rolled back from. This is used for verification.
  current_version: "1.2.4"

# --- Kubernetes Specific Settings (only applicable if platform is kubernetes) ---
kubernetes:
  # Namespace where the application is deployed.
  namespace: "default"

  # Deployment name.
  deployment_name: "YOUR_DEPLOYMENT_NAME"

  # Image tag to rollback to.
  image_tag: "1.2.3"

  # Number of replicas to verify after the rollback.
  replica_count: 3

# --- Docker Specific Settings (only applicable if platform is docker) ---
docker:
  # Docker compose file path.
  compose_file: "docker-compose.yml"

  # Service name to rollback.
  service_name: "YOUR_SERVICE_NAME"

# --- AWS ECS Specific Settings (only applicable if platform is aws_ecs) ---
aws_ecs:
  # ECS cluster name
  cluster_name: "YOUR_ECS_CLUSTER_NAME"

  # ECS service name
  service_name: "YOUR_ECS_SERVICE_NAME"

  # Task definition family name
  task_definition_family: "YOUR_TASK_DEFINITION_FAMILY"

# --- Manual Script Settings (only applicable if platform is manual_script) ---
manual_script:
  # Path to the script to execute for the rollback.
  script_path: "/path/to/rollback_script.sh"

  # Arguments to pass to the script.
  script_arguments: ["--rollback", "--version", "1.2.3"]

# --- Safety Checks ---
safety_checks:
  # List of checks to perform before initiating the rollback.
  checks:
    - type: "health_check"
      # URL to check for application health.
      url: "https://YOUR_APPLICATION_URL/health"
      # Expected HTTP status code for a healthy application.
      expected_status_code: 200
      # Timeout in seconds for the health check.
      timeout: 10

    - type: "database_check"
      # SQL query to execute.
      query: "SELECT COUNT(*) FROM users;"
      # Expected result from the query.
      expected_result: "example-value"

    - type: "metric_check"
      # Metric name to check.
      metric_name: "error_rate"
      # Maximum acceptable value for the metric.
      max_value: 0.01  # Example: 1% error rate
      # Monitoring system (e.g., prometheus, cloudwatch)
      monitoring_system: "prometheus"
      # Query to get the metric from the monitoring system.
      query: "sum(rate(http_requests_total{status=~'5..'}[5m])) / sum(rate(http_requests_total[5m]))"

# --- Notification Settings ---
notifications:
  # List of notification channels to send rollback status updates to.
  channels:
    - type: "slack"
      # Slack webhook URL.
      webhook_url: "YOUR_SLACK_WEBHOOK_URL"
      # Channel to send notifications to.
      channel: "#deployment-alerts"

    - type: "email"
      # Recipient email addresses.
      recipients: ["admin@example.com", "devops@example.com"]

# --- Advanced Settings ---
advanced:
  # Timeout in seconds for the entire rollback process.
  rollback_timeout: 3600 # 1 hour

  # Number of retries for failed operations.
  retries: 2

  # Delay in seconds between retries.
  retry_delay: 30
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall