operating-infra

description

Author, inspect, troubleshoot, and review infrastructure across IaC, Kubernetes, cloud resources, containers, CI/CD, and Linux hosts. Use when changing Terraform/OpenTofu, Kubernetes, Helm, Kustomize, Dockerfiles, GitHub Actions workflow/job/permissions semantics, AWS, GCP, Cloud Run, BigQuery, IAM, logs, instances, or service health. NOT for deploy/apply/rollback workflows (see deploying-infra). NOT for shell scripts, generic command pipelines, or only the shell body inside `run:` steps (see writing-shell).

name

operating-infra

Operate Infrastructure

Boundary

• Work from files, plans, logs, and read-only commands before changing anything.
• Do not run apply, delete, destroy, or rollback until identity, exact resources, blast radius, and plan/diff/inventory are shown and the user confirms.
• If the task is deployment, rollout, rollback, or production apply, use deploying-infra.
• If the task is only shell scripts, generic command pipelines, or the shell body inside a GitHub Actions run: step, use writing-shell.
• For GitHub Actions, workflow structure, triggers, jobs, permissions, runners, actions, environments, secrets, caching, concurrency, and policy stay here. Mixed workflow and shell-body changes compose with writing-shell.

Role behavior

• Write-capable: make minimal file changes and run safe validation. Stop before live mutation unless the user confirmed exact resources.
• Read-only: apply nothing; return proposed file changes, evidence, and validation commands.

Load references

Load every matching reference:

• Terraform/OpenTofu files, modules, state, or plans → terraform.md
• Kubernetes manifests or kustomization.yaml → kubernetes.md