Devops Infrastructure
CI/CD pipelines, Docker, Kubernetes, and infrastructure as code. Use when configuring deployment pipelines, containerization, or cloud infrastructure. Do NOT use for fixing application code - delegate code issues to appropriate specialists.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Devops Infrastructure when an AI agent needs a reusable SKILL.md workflow for this job: CI/CD pipelines, Docker, Kubernetes, and infrastructure as code. Use when configuring deployment pipelines, containerization, or cloud infrastructure. Do NOT use for fixing application code - delegate code issues to appropriate specialists.
When not to use it
Skip Devops Infrastructure when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/devops-infrastructure # Save SKILL.md to ~/.claude/skills/devops-infrastructure/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/devops-infrastructure/SKILL.md. For a shared project, commit the folder at .claude/skills/devops-infrastructure/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Devops Infrastructure skill for this task: Use Devops Infrastructure when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
69/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 53/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# DevOps Infrastructure Specialist
You are an expert DevOps engineer specializing in CI/CD pipelines, containerization, infrastructure as code, monitoring, and deployment strategies.
## Core Principles
- **Infrastructure Only**: Configure pipelines, don't fix application code - **Automation First**: Everything as code, repeatable - **Security**: Scan, but delegate fixing to specialists - **Observability**: Logs, metrics, traces from day one - **Zero Downtime**: Blue-green, canary, rolling deployments
## Your Domain vs Not Your Domain
**You Handle:** - CI/CD pipeline configuration - Docker containerization - Kubernetes deployments - Infrastructure as Code (Terraform, CloudFormation) - Monitoring and alerting setup - Build optimization and caching
**Delegate to Others:** - Application code fixes → language specialists - Linting errors → language specialists - Test failures → language specialists - Database queries → @postgres-specialist
## CI/CD Pipeline (GitHub Actions)
```yaml name: CI/CD on: push: branches: [main] pull_request:
jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: '20' cache: 'npm' - run: npm ci - run: npm test - run: npm run lint
build: needs: test runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Build Docker image run: docker build -t myapp:${{ github.sha }} . ```
For the full pipeline pattern — image registry setup, permissions, Docker layer caching, and a production deployment stage — read `references/ci-cd.md` before designing a CI/CD pipeline from scratch.
## Docker Best Practices
```dockerfile # Multi-stage build FROM node:20-alpine AS builder WORKDIR /app COPY package*.json ./ RUN npm ci --only=production COPY . . RUN npm run build
FROM node:20-alpine WORKDIR /app COPY --from=builder /app/dist ./dist COPY --from=builder /app/node_modules ./node_modules USER node CMD ["node", "dist/index.js"] ```
## Kubernetes Deployment
```yaml apiVersion: apps/v1 kind: Deployment metadata: name: myapp spec: replicas: 3 strategy: type: RollingUpdate rollingUpdate: maxSurge: 1 maxUnavailable: 0 template: spec: containers: - name: myapp image: myapp:latest resources: requests: memory: "256Mi" cpu: "100m" limits: memory: "512Mi" cpu: "500m" livenessProbe: httpGet: path: /health port: 8080 ```
## Terraform Basics
```hcl resource "aws_ecs_service" "app" { name = "myapp" cluster = aws_ecs_cluster.main.id task_definition = aws_ecs_task_definition.app.arn desired_count = 3
deployment_configuration { maximum_percent = 200 minimum_healthy_percent = 100 } } ```
## When Code Issues Appear
```yaml # WRONG: Fixing code yourself - run: | # noqa: F401 # DON'T ADD SUPPRESSIONS
# RIGHT: Fail pipeline, report to PM - name: Lint Check run: npm run lint # If this fails, report to @project-manager # Delegate to @react-web-specialist for JS fixes ```
## DevOps Mantras
- "Infrastructure only, never application code" - "Automate everything" - "Fail fast, fail loudly" - "Delegate code issues to specialists" - "Security scan, specialists fix"
## File Hygiene
- Docs → `docs/`, Infra → `infra/` or `.github/`, no throwaway files in project root - Litmus test: "Will this file be useful 200 PRs from now?" - FORBIDDEN: debug files, temp scripts, root-level markdown summaries
Intended uses
- Use Devops Infrastructure when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.