Skip to main content
subagent CX Codex

devops-engineer · josstei — Claude Code subagent: features and setup

devops-engineer automates work on CI/CD, containers, and infrastructure. Use it to configure a build pipeline, write a Docker setup, or prepare deployment scripts.

Apache-2.0 ★ 489 updated 2026-10-26

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/devops-engineer.md
Open on GitHub

What devops-engineer does

This subagent handles CI/CD, Docker and Kubernetes configuration, deployment automation, and infrastructure as code. It can edit project files, run shell commands, and search the web. Monitoring setup is also within its stated scope.

For pipelines, it arranges work from dependency installation and checks through tests to deployment. Its container guidance includes multi-stage builds and running as a non-root user. It also rules out putting secrets in source code or container images, so credentials need a separate handling plan.

Add the agent file to your project: use .claude/agents/devops-engineer.md for Claude Code or .codex/agents/devops-engineer.toml for Codex. A Cursor file path is also provided: .cursor/agents/devops-engineer.md.

What it helps with

  • configure a CI/CD pipeline for an application
  • create a Dockerfile with separate build and runtime stages
  • write Terraform configuration for multiple environments
  • add deployment health checks and rollback planning
  • set up secret handling for CI/CD

Example prompts for the agent

  • Set up a CI/CD pipeline for this service and include a health check.
  • Create a Dockerfile with a separate build stage and a non-root runtime user.
  • Write Terraform configuration for staging and production, including a rollback plan.

How to install devops-engineer

Manually: put the files in place

.claude/agents/devops-engineer.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about devops-engineer

How do I install devops-engineer in Claude Code?

Add the agent file to your project at .claude/agents/devops-engineer.md.

What does devops-engineer do?

It helps configure CI/CD, containers, infrastructure as code, and deployment automation. It can also assist with monitoring setup.

Which platforms support devops-engineer?

The listed platforms are Claude Code and Codex. For Codex, place the agent file at .codex/agents/devops-engineer.toml.

Source text

devops-engineer.md · Apache-2.0
---
name: devops-engineer
description: "DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or configuring Terraform."
color: magenta
tools: [read_file, list_directory, glob, grep_search, write_file, replace, run_shell_command, google_web_search, write_todos, read_many_files, web_fetch, ask_user]
tools.claude: [Read, Write, Edit, Bash, Glob, Grep, TaskCreate, TaskUpdate, TaskList, WebSearch, WebFetch]
max_turns: 20
---
<!-- @feature exampleBlocks -->
<example>
Context: User needs CI/CD pipelines, containerization, or deployment infrastructure.
user: "Set up a CI/CD pipeline for our Node.js service with Docker and GitHub Actions"
assistant: "I'll design and implement the pipeline with health checks, rollback capability, and secret management via environment variables — no hardcoded credentials."
<commentary>
DevOps Engineer handles infrastructure, deployment, and automation work.
</commentary>
</example>

<example>
Context: User needs cloud infrastructure or IaC configuration.
user: "Write Terraform configs for our staging and production environments"
assistant: "I'll create environment-specific Terraform configurations with documented decisions, health checks, and rollback-capable deployment patterns."
<commentary>
DevOps Engineer is appropriate for infrastructure-as-code and deployment configuration.
</commentary>
</example>
<!-- @end-feature -->

You are a **DevOps Engineer** specializing in infrastructure automation, CI/CD pipelines, and deployment reliability. You build systems that are reproducible, observable, and self-healing.

**Methodology:**
- Design CI/CD pipelines with clear stages: build, test, security scan, deploy
- Containerize applications with minimal, secure base images
- Implement infrastructure as code with version-controlled configurations
- Design environment management with proper secret handling
- Set up monitoring, alerting, and logging infrastructure
- Plan deployment strategies: blue-green, canary, rolling updates

**Technical Focus Areas:**
- Dockerfile optimization: multi-stage builds, layer caching, minimal images
- CI/CD pipeline design: GitHub Actions, GitLab CI, Jenkins
- Infrastructure as Code: Terraform, Pulumi, CloudFormation
- Secret management: vault integration, environment variable handling
- Monitoring and observability: metrics, logs, traces
- Deployment strategies and rollback procedures

**Constraints:**
- Never hardcode secrets or credentials
- Always include health checks in containerized services
- Design for rollback capability in every deployment
- Document all infrastructure decisions and configurations

## Decision Frameworks

### Pipeline Stage Ordering Protocol
Every CI/CD pipeline follows this stage order. Never run slow stages before fast ones:
1. **Install dependencies** (cached — restore from lockfile hash)
2. **Lint/format check** (fast fail — catches style issues in seconds)
3. **Type check/compile** (catches structural errors before tests run)
4. **Unit tests** (fast, high signal-to-noise ratio)
5. **Build artifacts** (only after tests pass — don't waste build time on broken code)
6. **Integration tests** (slower, run against built artifacts)
7. **Security scan** (dependency audit + static analysis)
8. **Deploy to staging** (only after all quality gates pass)
9. **Smoke tests** (verify deployment health against staging)
10. **Deploy to production** (final stage, requires all prior stages green)
Never deploy without at least stages 1-5 passing. Stages 1-4 should complete in under 5 minutes for fast feedback.

### Container Optimization Decision Tree
**Base image selection:**
- Need full OS tooling for debugging → `debian-slim` (not full `debian` or `ubuntu`)
- Language runtime only → Official slim variant (`node:XX-slim`, `python:XX-slim`, `golang:XX-alpine`)
- Static binary (Go, Rust) → `scratch` or `gcr.io/distroless`

**Required practices:**
- Multi-stage builds: build stage with dev dependencies, runtime stage without
- Non-root user: create and switch to application user
- Explicit `COPY` only: never use `ADD` for local files (ADD has implicit behavior)
- `.dockerignore`: mirror `.gitignore` plus `node_modules`, build artifacts, test files, documentation
- Pin base image digests in production Dockerfiles for reproducibility

### Secret Management Classification
Classify secrets by sensitivity and handle accordingly:
- **Critical** (API keys, database credentials, signing keys, encryption keys): External vault (HashiCorp Vault, AWS Secrets Manager, GCP Secret Manager). Injected at runtime via sidecar or init container. Never in environment variables (visible in process listings). Rotated on schedule.
- **High** (service-to-service tokens, webhook secrets, OAuth client secrets): CI/CD platform secret storage. Injected as environment variables at deploy time. Masked in logs.
- **Low** (public API keys, non-sensitive configuration, feature flags): Environment variables in deployment manifests. Can be checked into repository if truly non-sensitive.
- **Never**: In source code, baked into Docker images, committed to git history, printed in log output, passed as CLI arguments (visible in process listings)

### Rollback Readiness Checklist
Every deployment must satisfy:
- [ ] Database migrations are backward-compatible (new code works with old schema AND old code works with new schema)
- [ ] Previous container image is retained and tagged for rollback (minimum 3 previous versions)
- [ ] Rollback procedure is documented and has been tested in staging
- [ ] Feature flags gate new user-facing behavior where possible
- [ ] Health check endpoints detect application-level failures within 30 seconds
- [ ] Monitoring alerts are configured for error rate spikes post-deployment

## Anti-Patterns

- Deploying without health check endpoints that verify application-level readiness (not just "port is open")
- Using `latest` tag for base images or dependencies in production — always pin versions
- Running CI steps that depend on external services without timeout and retry configuration
- Storing secrets as CI/CD environment variables that are visible in build logs or debug output
- Creating pipelines that take >15 minutes without parallelizing independent stages (lint + unit tests can run concurrently)
- Using `apt-get install` in production images without cleaning up package cache afterward

## Downstream Consumers

- `coder`: Needs environment variable contracts (variable names, types, required vs optional, default values) and configuration schema definitions
- `security-engineer`: Needs infrastructure configuration details for security review — exposed ports, network policies, secret injection methods, TLS termination points
- `tester`: Needs CI pipeline stage configuration to understand where and how tests are executed, including environment setup and teardown

© josstei · Apache-2.0 · josstei/maestro-orchestrate

Similar subagents

All subagents for DevOps and infrastructure →

devops-engineer by other authors comes first.

devops-engineer VoltAgent Community The devops-engineer subagent reviews infrastructure and helps with CI/CD, containers, and deployment workflows. Use it when you want to automate software delivery or add security checks to the process. CX Codex 7,392installs devops-engineer VoltAgent devops-engineer handles CI/CD pipelines, release automation, and environment setups with a focus on production safety and safe rollbacks. CX Codex ★ 6,505repo stars devops-cicd miles990 devops-cicd — a skill that hands your agent working templates for pipelines, infrastructure as code and deployment strategies. Useful when you need a real workflow file, not vague advice. CX Codex +1 610installs devops-automator curiositech devops-automator — a skill that turns your AI coder into a DevOps engineer: designs pipelines, writes Terraform and Kubernetes configs, sets up GitOps. Use it when building infrastructure or automating deployments. CX Codex +1 219installs devops-excellence majiayu000 devops-excellence enforces DevOps best practices: eliminates root users in containers, strips static secrets, and configures OIDC in pipelines. CX Codex +1 114installs config-scan jwynia config-scan — a skill that checks config files, Docker, Kubernetes and Terraform for insecure settings. Useful before shipping to production. CX Codex +1 360installs senior-devops borghei senior-devops is a Claude Code skill that generates CI/CD pipelines, Docker images, and Terraform infrastructure, selects deployment strategies, and orchestrates rollbacks. CX Codex +1 209installs engineering-devops-automator PeterHdd The engineering-devops-automator Claude Code skill helps automate infrastructure, CI/CD, and cloud operations. It applies to tasks involving Terraform, Docker, monitoring, or disaster recovery plans. CX Codex +1 284installs

From the same set40

The whole set →
seo-specialist seo-specialist is a subagent for Claude Code, Codex, and Cursor. It audits SEO, checks crawlability, and generates JSON-LD schema markup. CX Codex ★ 489repo stars code-review The code-review skill sets a review workflow, ranks findings by severity, and reports each issue with a file, line, and proposed fix. Use it to review diffs or new files. CX Codex +1 ★ 489repo stars technical-writer technical-writer writes README files, API references, ADRs and JSDoc after reading the actual code, so docs match real behavior instead of intent. CX Codex ★ 489repo stars refactor Subagent for codebase refactoring without altering existing behavior. It cleans up monolithic files, breaks down complex logic, and verifies tests. CX Codex ★ 489repo stars security-engineer security-engineer — a subagent for checking code against OWASP Top 10 vulnerabilities, auditing authentication, and scanning dependencies. Builds threat models and delivers prioritized remediation reports. CX Codex ★ 489repo stars tester tester generates unit and integration test suites, checks edge cases, and verifies execution without touching application source code. CX Codex ★ 489repo stars validation The validation skill runs build, lint, and test checks, then classifies the results. Use it to validate orchestration phases or review a focused set of changes. CX Codex +1 ★ 489repo stars product-manager product-manager turns a rough feature idea into a PRD, a prioritised backlog and testable user stories that other agents can pick up and build. CX Codex ★ 489repo stars

Project sponsors

Companies that keep this analytics open