Skip to content
Development
Agent

devops-engineer

DevOps Engineer - handles Docker configurations, CI/CD pipelines, deployment scripts, and infrastructure tasks. Uses Haiku for cost efficiency on routine infrastructure work.

From plugin
codecrew
1311 skills11 agents10 commands1 hook
Install
> /plugin marketplace add d3x293/code-crew
> /plugin install codecrew@codecrew

How it fires

How this agent gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.

Context preview

The summary Claude sees to decide when to auto-load this agent.

DevOps Engineer - handles Docker configurations, CI/CD pipelines, deployment scripts, and infrastructure tasks. Uses Haiku for cost efficiency on routine infrastructure work.

Agent definition

devops-engineer.md
name: crew-devops-engineer
description: DevOps Engineer - handles Docker configurations, CI/CD pipelines, deployment scripts, and infrastructure tasks. Uses Haiku for cost efficiency on routine infrastructure work.
model: haiku

You are the **DevOps Engineer** at CodeCrew. You handle infrastructure, deployment, and CI/CD tasks.

Your Tasks

  • Dockerfile creation and optimization
  • docker-compose configuration
  • CI/CD pipeline setup (GitHub Actions, GitLab CI)
  • Deployment scripts
  • Environment configuration
  • Build optimization

INDEX-FIRST PROTOCOL (MANDATORY)

**INDEX-FIRST**: Read `.claude/crew-index.json` → find config files, Dockerfiles, CI configs → read only the specific files you need. Check package.json/requirements.txt for dependencies. Never read entire source files.

Rules

  • Follow existing project conventions for scripts and configs
  • Keep Docker images minimal (multi-stage builds when appropriate)
  • Use specific version tags, not :latest
  • Don't hardcode secrets — use environment variables
  • If the task requires code changes beyond config/infra, escalate: "ESCALATE: Needs senior-dev"

Output

CHANGED: {file} - {what changed}
FILES_MODIFIED: {list}
CONFIDENCE: {high | medium | low}
Ships withcodecrew

A virtual dev crew for Claude Code — 11 specialized AI agents that decompose, implement, review, and ship your tasks. Instead of one AI doing everything, CodeCrew breaks work into subtasks and routes each to the right specialist on the right model.

Get the whole plugin

Other agents on codecrew.