borghei/Claude-Skills / engineering/senior-devops
senior-devops
VerifiedDevOps for CI/CD, containers, Kubernetes, and Terraform. Use when building pipelines, containerizing apps, managing clusters, provisioning cloud infra, deploying with blue- green/canary, or handling infrastructure incidents.
Senior DevOps Engineer
The agent generates CI/CD pipelines, scaffolds Terraform infrastructure, and manages deployments with strategy selection, health checks, and rollback support.
Core Capabilities
- CI/CD pipeline generation — fail-fast, cached, immutable-artifact pipelines for GitHub Actions, GitLab CI, Jenkins, and CircleCI with matrix testing and promotion gates.
- Containerization — production multi-stage Dockerfiles with non-root users, healthchecks, and runtime secret injection.
- Kubernetes deployment — Deployments with liveness/readiness/startup probes, resource limits, and security context; Helm, HPA/VPA/KEDA, network policies, RBAC.
- Infrastructure as Code — Terraform module scaffolding, remote state with locking, environment separation, and CI drift detection.
- Deployment strategies — rolling, blue-green, canary, and feature-flag rollouts with health checks and automated rollback.
- Monitoring & SLOs — Four Golden Signals dashboards, SLO/error-budget targets, and deployment-freeze recommendations.
When to Use
- Building or optimizing a CI/CD pipeline.
- Containerizing an app or deploying to Kubernetes.
- Provisioning cloud infrastructure with Terraform.
- Choosing and executing a deployment strategy (blue-green/canary).
- Handling an infrastructure incident or rollback.
Clarify First
Before generating pipelines or infra, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
- CI/CD platform: GitHub Actions / GitLab CI / Jenkins / CircleCI (changes the generated pipeline config).
- Deployment strategy: rolling / blue-green / canary / feature-flag (sets health checks and rollback in the deployment plan).
- Target cloud & IaC scope: provider and which Terraform modules are needed (drives
terraform_scaffolder).
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
Tools
All three are Python standard library only, read local files, make no network calls and never run other programs. Each prints readable text by default and JSON with --json, and exits 2 with a one-line error: message on bad input (0 otherwise).
| Tool | Purpose | Command |
|---|---|---|
pipeline_generator.py | Detect the stack (Node with npm/yarn/pnpm, Python with pip/uv/poetry, Go, Rust, Maven, Gradle, Dockerfile) and generate a CI config with cached install, lint, test, build and optional Docker build | python scripts/pipeline_generator.py <project-path> --json |
terraform_scaffolder.py | Scaffold a Terraform module, per-environment root modules with remote state and locking, tfvars and a README | python scripts/terraform_scaffolder.py <target-path> --json |
deployment_manager.py | Read a JSON deployment spec and plan the release: strategy with reasons, steps, probe thresholds, rollback triggers and runbook | python scripts/deployment_manager.py <spec.json> --json |
Flags.
pipeline_generator.py:--platform github-actions|gitlab-ci|circleci|jenkins(defaultgithub-actions),--no-docker,--output/-o PATH(relative to the project; refuses to overwrite without--force),--verbose/-v. Without--outputit only prints. Version files are honoured only for Node 18 to 26 and Python 3.8 to 3.14 (otherwise Node 22 or Python 3.12, with a warning). GitHub Actions are pinned to major-version tags by design; pin to commit SHAs for high-assurance repositories (seereferences/cicd_pipeline_guide.md).terraform_scaffolder.py:--provider aws|gcp|azure(S3 + DynamoDB, GCS or azurerm backend),--name(defaultapp),--envs(defaultdev,staging,prod),--force,--dry-run,--verbose/-v. Refuses to write if any target.tfor.tfvarsfile exists, unless--force; an existingREADME.mdor.gitignoreis always kept, never overwritten. Names must be lowercase with single inner hyphens (orders-api). Azure scaffolds include thesubscription_idthat azurerm 4.x requires, keep the environment suffix in the 24-character storage account name, and limit environments to 12 characters without hyphens. The generated README notes thatdevsetsforce_destroy = trueand that bucket names must be globally unique.deployment_manager.py:--strategy rolling|blue-green|canaryto override the choice,--exampleto print a sample spec,--output/-o PATHto save the JSON plan,--verbose/-vto include the resolved spec. It only plans; it executes nothing.servicemust be a Kubernetes name andversionan image tag, because both appear in the runbook commands.
Sample inputs in assets/: sample-node-app/ and sample-python-app/ (tiny projects), and deploy-canary.json, deploy-blue-green.json, deploy-rolling.json (one spec per strategy).
Example output.
$ python scripts/pipeline_generator.py assets/sample-node-app
Detected: node 22 (npm), Docker: yes
Stages: install, lint, test, build, docker
# .github/workflows/ci.yml
name: CI
on:
push:
branches:
- main
pull_request: {}
permissions:
contents: read
...
$ python scripts/terraform_scaffolder.py ./infra --provider aws --name orders-api --envs dev,prod
Created 18 files (aws, s3 backend, envs: dev, prod)
infra/
.gitignore
README.md
environments/
dev/
backend.tf
main.tf
...
$ python scripts/deployment_manager.py assets/deploy-canary.json
Deployment plan: checkout-api 2.3.1 -> 2.4.0 [canary]
Why: User-facing, medium risk, 400 rps: enough traffic to judge a small slice before exposing everyone.
Steps:
1. deploy canary: Start checkout-api:2.4.0 next to the stable version with 0% traffic; wait for readiness.
2. shift 5% [traffic 5%] [bake 10 min]: Route 5% to 2.4.0; compare canary against stable on the rollback triggers for 10 min.
...
Automatic rollback when any of these holds:
- error rate (5xx / total) > 0.8% (2 consecutive 1-min windows)
- p99 latency > 330 ms (3 consecutive 1-min windows)
...
deploy-blue-green.json picks blue-green (high risk, 1-minute rollback tolerance, capacity can double) and deploy-rolling.json picks rolling (low risk, internal worker).
References
Load the reference that matches the task — keep this file lean and pull detail on demand:
- references/devops-workflows-and-operations.md — the three end-to-end workflows (containerize & deploy, Terraform IaC, CI/CD design) with worked Dockerfile/YAML/HCL examples, the deployment-strategy selection matrix and canary ladder, monitoring essentials (Four Golden Signals, SLO targets), anti-patterns, and the troubleshooting table. Read when executing any workflow or diagnosing an incident.
- references/cicd_pipeline_guide.md — stage order, lockfile installs and cache keys per stack, platform differences, least-privilege and pinning defaults, review checklist. Read with
pipeline_generator.pyoutput. - references/infrastructure_as_code.md — module and environment layout, version pinning, remote state and locking per backend, variable validation, plan/apply workflow and drift detection. Read with
terraform_scaffolder.pyoutput. - references/deployment_strategies.md — the strategy selection rules, canary ladder and bake-time formula, probe settings, rollback triggers, runbooks and expand/contract migrations. Read with
deployment_manager.pyoutput. - references/kubernetes_patterns.md — Helm charts, HPA/VPA/KEDA decisions, network policies, and RBAC patterns.
- references/cloud_platform_guide.md — AWS/GCP/Azure service comparison, multi-cloud strategy, and cost optimization.
Scope & Limitations
In Scope:
- Generating a starter CI pipeline from a project's files, scaffolding a Terraform module with environments and remote state, and planning a rolling, blue-green or canary release from a spec (the three scripts).
- Guidance and worked examples for containerizing and deploying an application, Terraform infrastructure as code and CI/CD pipeline design, in
references/devops-workflows-and-operations.md. - Deployment strategy selection (rolling, blue-green, canary, feature flags), monitoring essentials (Four Golden Signals, SLO targets), anti-patterns and troubleshooting.
- Kubernetes patterns (Helm structure, HPA, VPA and KEDA, network policies, RBAC, container security) in
references/kubernetes_patterns.md. - Cloud service comparison, cost optimization, alerting rules and incident runbook templates in
references/cloud_platform_guide.md.
Out of Scope:
- Linting existing pipelines, cache tuning and deploy-stage generation (see
engineering/ci-cd-pipeline-builder/). - Static review of Terraform modules and security rules (see
engineering/terraform-patterns/) and of Helm charts (seeengineering/helm-chart-builder/). - Running an incident (see
engineering/incident-commander/) and designing observability (seeengineering/observability-designer/). - Applying anything to a cloud account or cluster. The skill has no cloud, cluster or CI access.
Important Caveats:
pipeline_generator.pyreads only the project root and generates for the first stack it finds; a monorepo needs one run per package. It stops at the Docker build and does not push images or deploy.terraform_scaffolder.pywrites placeholder state bucket names (CHANGE-ME) and one starter storage resource; replace both beforeterraform init.deployment_manager.pyplans from the numbers in the spec. Rollback thresholds are only as good as thebaselineandslosupplied.- Cloud services, CI platform syntax and Kubernetes APIs change often, so examples need checking against current provider documentation before use.
Integration Points
| Skill | Integration |
|---|---|
senior-secops | Security scanning in CI/CD, container image scanning, compliance checks |
senior-architect | Infrastructure design decisions, service topology |
senior-backend | Application containerization, health endpoints, config management |
code-reviewer | Terraform plan review, pipeline config review |
incident-commander | Incident escalation, postmortem, rollback procedures |
Last Updated: June 2026 Version: 2.2.0
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |