CD Pipeline Generator Agent Skill

Generate GitHub Actions deployment workflows for automated deployment to staging and production environments on cloud platforms (AWS, GCP, Azure). Use when setting up continuous deployment pipelines, creating deployment automation, or configuring multi-environment deployment strategies. Includes templates for environment-specific deployments with approval gates, secrets management, and rollback capabilities.

3k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

141

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill cd-pipeline-generator

The instruction itself

14 sections, as written by the author

CD Pipeline Generator

Overview

Generate production-ready GitHub Actions deployment workflows that automate deployments to staging and production environments with environment protection rules, approval gates, and secrets management.

Workflow

1. Identify Deployment Target

Determine the cloud platform and deployment method:

AWS: ECS, Elastic Beanstalk, EC2, Lambda
GCP: Cloud Run, App Engine, Compute Engine, Cloud Functions
Azure: App Service, Container Instances, Functions

2. Select Template

Use the appropriate template from assets/ based on cloud platform:

deploy-aws.yml - AWS deployments (ECS, Elastic Beanstalk, Lambda)
deploy-gcp.yml - GCP deployments (Cloud Run, App Engine)
deploy-azure.yml - Azure deployments (App Service, Container Instances)

3. Configure Environments

Set up GitHub environment protection rules for staging and production:

Staging environment:

Auto-deploy on merge to main/master
No approval required
Use staging secrets and variables

Production environment:

Manual approval required
Deploy on workflow_dispatch or tag push
Use production secrets and variables
Optional: Restrict to specific branches

4. Configure Secrets

Add required secrets to GitHub repository settings (Settings → Secrets and variables → Actions):

AWS:

AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
AWS_REGION

GCP:

GCP_PROJECT_ID
GCP_SERVICE_ACCOUNT_KEY

Azure:

AZURE_CREDENTIALS
AZURE_SUBSCRIPTION_ID

5. Customize Deployment Steps

Adapt the template to project-specific deployment needs:

Build artifacts: Add build steps before deployment

- name: Build application
  run: npm run build  # or: python -m build, go build, cargo build

Docker images: Build and push container images

- name: Build Docker image
  run: docker build -t $IMAGE_NAME:$TAG .

- name: Push to registry
  run: docker push $IMAGE_NAME:$TAG

Database migrations: Run migrations before deployment

- name: Run migrations
  run: npm run migrate  # or: alembic upgrade head, rails db:migrate

Health checks: Verify deployment success

- name: Health check
  run: curl -f https://$DEPLOYMENT_URL/health || exit 1

6. Set Deployment Triggers

Configure when deployments run:

Staging: Auto-deploy on push to main

on:
  push:
    branches: [main]

Production: Manual trigger or tag-based

on:
  workflow_dispatch:
  push:
    tags:
      - 'v*'

7. Place Workflow File

Create deployment workflow at .github/workflows/deploy.yml. If multiple deployment workflows are needed (e.g., separate staging and production), use descriptive names:

.github/workflows/deploy-staging.yml
.github/workflows/deploy-production.yml

Template Features

All templates include:

Environment separation: Distinct staging and production deployments
Approval gates: Production deployments require manual approval
Secrets management: Secure credential handling via GitHub secrets
Deployment status: Clear success/failure reporting
Rollback support: Easy revert to previous versions
Conditional execution: Deploy only when tests pass

Security Best Practices

Never commit credentials or API keys to the repository
Use GitHub environments to scope secrets appropriately
Enable required reviewers for production deployments
Use OIDC authentication instead of long-lived credentials when possible
Implement deployment windows for production (e.g., business hours only)
Add deployment notifications to Slack/email

Customization Examples

Add deployment notification:

- name: Notify deployment
  if: always()
  uses: 8398a7/action-slack@v3
  with:
    status: ${{ job.status }}
    text: 'Deployment to ${{ github.event.inputs.environment }} ${{ job.status }}'
  env:
    SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK }}

Add rollback capability:

- name: Rollback on failure
  if: failure()
  run: |
    echo "Deployment failed, rolling back..."
    # Platform-specific rollback commands

Restrict production deployment time:

- name: Check deployment window
  run: |
    HOUR=$(date +%H)
    if [ $HOUR -lt 9 ] || [ $HOUR -gt 17 ]; then
      echo "Deployments only allowed 9 AM - 5 PM"
      exit 1
    fi

Tips

Start with staging deployments to validate the workflow
Use environment-specific configuration files (e.g., config.staging.json, config.production.json)
Implement blue-green or canary deployments for zero-downtime updates
Add deployment metrics and monitoring
Document rollback procedures in the repository
Test deployment workflows in a separate test environment first

Other skills for the same job

different authors, same section of the catalogue

Azure Kubernetes Automatic Readiness

by microsoft

vendor ×3

Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.

Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.

Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).

Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).

Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).

This skill should be used when working with LaminDB, an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR. Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakehouses, or ensuring data lineage and reproducibility in biological research. Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies.

Latch platform for bioinformatics workflows. Build pipelines with Latch SDK, @workflow/@task decorators, deploy serverless workflows, LatchFile/LatchDir, Nextflow/Snakemake integration.

Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.

17k tokens

How to use it

Copy the folder

Take arabelatso/cd-pipeline-generator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.