Devops Deployment
Stand up GitHub Actions, Docker images, Helm/Kubernetes deploys, and Terraform IaC patterns when you are ready to ship without hiring a platform team.
Overview
Devops-deployment is an agent skill most often used in Ship (also Operate) that sets up CI/CD, Docker, Kubernetes/Helm, and Terraform deployment patterns for solo builders.
Install
npx skills add https://github.com/yonatangross/orchestkit --skill devops-deploymentWhat is this skill?
- CI/CD pipeline setup frameworks (GitHub Actions-first)
- Docker and docker-compose containerization patterns
- Kubernetes and Helm deployment guidance
- Terraform and infrastructure-as-code path patterns
- Scoped to .github/workflows, Dockerfile*, k8s/**, terraform/** in the repo
- Path patterns cover .github/workflows, Dockerfile*, docker-compose, k8s/**, helm/**, and *.tf
- Requires Claude Code 2.1.76+ per skill metadata
Adoption & trust: 703 installs on skills.sh; 183 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have working code locally but no reliable pipeline, container story, or IaC layout—and every deploy feels manual and scary.
Who is it for?
Indie developers shipping SaaS or APIs who need GitHub Actions plus Docker or K8s without a dedicated DevOps hire.
Skip if: No-code-only launches with zero repo access, or teams that only need copy/marketing skills with no infrastructure files to edit.
When should I use this skill?
Setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code (GitHub Actions, Docker, Helm, Terraform).
What do I get? / Deliverables
You get opinionated DevOps frameworks and file-scoped patterns your agent can apply to workflows, Dockerfiles, and terraform/k8s dirs for repeatable releases.
- CI/CD workflow definitions
- Dockerfile or compose configuration
- Kubernetes/Helm or Terraform scaffolding aligned to repo paths
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
CI/CD and first production deploy are the bridge from built code to something users can hit—canonical ship work before ongoing operate chores. Ship launch subphase is where release pipelines, containerization, and environment promotion land in the journey taxonomy.
Where it fits
Add a workflow that builds a Docker image and pushes to your registry on main.
Extend Terraform modules when you add a second environment without duplicating state mistakes.
Introduce docker-compose for local dependencies before wiring production Helm values.
How it compares
In-repo DevOps guidance skill—not a managed PaaS deploy button or generic brainstorming workflow.
Common Questions / FAQ
Who is devops-deployment for?
Solo and small teams using Claude Code (OrchestKit) who own their repo and need CI/CD, containers, and cloud deploy patterns.
When should I use devops-deployment?
In ship launch when you add GitHub Actions or Docker; in operate infra when you change Terraform, Helm charts, or promotion strategy between environments.
Is devops-deployment safe to install?
Review Security Audits on this Prism page; the skill reads infra files and may suggest shell/docker commands—never auto-apply production terraform without your review.
SKILL.md
READMESKILL.md - Devops Deployment
# DevOps & Deployment Skill Comprehensive frameworks for CI/CD pipelines, containerization, deployment strategies, and infrastructure automation. > **Note:** If `disableSkillShellExecution` is enabled (CC 2.1.91), the Docker install check won't run. Verify Docker is available for container operations: `docker --version`. ## Overview - Setting up CI/CD pipelines - Containerizing applications - Deploying to Kubernetes or cloud platforms - Implementing GitOps workflows - Managing infrastructure as code - Planning release strategies ## Pipeline Architecture ``` ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │ Code │──>│ Build │──>│ Test │──>│ Deploy │ │ Commit │ │ & Lint │ │ & Scan │ │ & Release │ └─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘ │ │ │ │ v v v v Triggers Artifacts Reports Monitoring ``` ## Key Concepts ### CI/CD Pipeline Stages 1. **Lint & Type Check** - Code quality gates 2. **Unit Tests** - Test coverage with reporting 3. **Security Scan** - npm audit + Trivy vulnerability scanner 4. **Build & Push** - Docker image to container registry 5. **Deploy Staging** - Environment-gated deployment 6. **Deploy Production** - Manual approval or automated ### Container Best Practices **Multi-stage builds** minimize image size: - Stage 1: Install production dependencies only - Stage 2: Build application with dev dependencies - Stage 3: Production runtime with minimal footprint **Security hardening**: - Non-root user (uid 1001) - Read-only filesystem where possible - Health checks for orchestrator integration ### Kubernetes Deployment **Essential manifests**: - Deployment with rolling update strategy - Service for internal routing - Ingress for external access with TLS - HorizontalPodAutoscaler for scaling **Security context**: - `runAsNonRoot: true` - `allowPrivilegeEscalation: false` - `readOnlyRootFilesystem: true` - Drop all capabilities ### Deployment Strategies | Strategy | Use Case | Risk | |----------|----------|------| | **Rolling** | Default, gradual replacement | Low - automatic rollback | | **Blue-Green** | Instant switch, easy rollback | Medium - double resources | | **Canary** | Progressive traffic shift | Low - gradual exposure | **Rolling Update** (Kubernetes default): ```yaml strategy: type: RollingUpdate rollingUpdate: maxSurge: 25% maxUnavailable: 0 # Zero downtime ``` ### Secrets Management Use External Secrets Operator to sync from cloud providers: - AWS Secrets Manager - HashiCorp Vault - Azure Key Vault - GCP Secret Manager --- ## References ### Docker Patterns **Load: `Read("${CLAUDE_SKILL_DIR}/references/docker-patterns.md")`** Key topics covered: - Multi-stage build examples with 78% size reduction - Layer caching optimization - Security hardening (non-root, health checks) - Trivy vulnerability