Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/devops/deployment-pipeline-orchestrator/skills/orchestrating-deployment-pipelines

orchestrating-deployment-pipelines

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

Orchestrating Deployment Pipelines

Overview

Orchestrate multi-stage deployment pipelines that coordinate builds, tests, approvals, and releases across environments (dev, staging, production). Implement deployment strategies including blue-green, canary, rolling updates, and feature flags using Kubernetes, cloud-native services, and CI/CD platforms.

Prerequisites

  • CI/CD platform configured (GitHub Actions, GitLab CI, Jenkins, ArgoCD)
  • Kubernetes cluster with kubectl access or cloud deployment target (ECS, Cloud Run, App Engine)
  • Container registry with built and tagged images ready for deployment
  • Environment-specific configuration (secrets, environment variables) stored securely
  • Monitoring and alerting configured to detect deployment failures

Instructions

  1. Define the deployment topology: target environments, promotion flow (dev -> staging -> production), and approval gates
  2. Select deployment strategy per environment: rolling update for staging, canary or blue-green for production
  3. Generate deployment manifests (Kubernetes Deployments, Services, Ingress) or cloud service configurations
  4. Implement pre-deployment checks: database migration status, dependency health, configuration validation
  5. Configure canary analysis: route 5-10% of traffic to new version, monitor error rate and latency for 15 minutes before full rollout
  6. Add post-deployment verification: smoke tests, health check endpoints, synthetic monitoring
  7. Implement automated rollback triggers: revert if error rate exceeds 1% or P99 latency doubles during canary phase
  8. Set up deployment notifications: Slack messages with deployment status, version, environment, and commit link
  9. Document the deployment runbook with manual intervention procedures for edge cases

Output

  • Deployment pipeline configurations (GitHub Actions workflows, ArgoCD Applications)
  • Kubernetes manifests with deployment strategy annotations
  • Canary analysis configuration (Flagger, Argo Rollouts)
  • Pre/post-deployment hook scripts
  • Deployment runbook with rollback procedures

Error Handling

ErrorCauseSolution
ImagePullBackOffImage tag not found in registry or auth failureVerify image exists with docker manifest inspect; check imagePullSecrets
CrashLoopBackOffApplication failing to start in new versionCheck pod logs with kubectl logs; verify environment variables and config maps
Canary analysis failedError rate or latency exceeded threshold during canaryAutomatic rollback triggered; investigate logs from canary pods before retrying
Deployment stuck in ProgressingInsufficient resources or pod scheduling failureCheck kubectl describe deployment for events; verify resource requests and node capacity
Database migration failedSchema conflict or lock timeoutRun migrations independently before deployment; add retry logic and connection timeout

Examples

  • "Create a deployment pipeline that builds on PR merge, deploys to staging automatically, runs integration tests, then requires manual approval for production with canary rollout."
  • "Set up Argo Rollouts for a Kubernetes deployment with 10% canary traffic, Prometheus-based analysis, and automatic rollback on error rate > 0.5%."
  • "Generate a blue-green deployment for an ECS service with ALB target group switching and automatic rollback on health check failure."

Resources

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