deploying-infra git:20260603.f0f4806B

Immutable. This exact content is served forever at /api/v1/blob/78f8c235213c4f44.

---
description:
  Validate infrastructure changes and, after explicit confirmation, apply Terraform,
  Helm, Kustomize, or Kubernetes deployments. Use when the user says "deploy",
  "deploy to staging", "terraform apply", "helm upgrade", "kubectl apply",
  "rollout", "deploy check", "validate deployment", or "validate infrastructure".
  Dockerfiles and GitHub Actions are validate-only here. NOT for ongoing service
  troubleshooting, cloud inspection, rollback investigation, or authoring infra from
  scratch; use operating-infra for those.
name: deploying-infra
targets:
  - claude
---

# Deploy Infrastructure

Validate first. Apply only after explicit confirmation. Never invent deploy paths,
release names, workspaces, namespaces, accounts, or environments.

## Scope

Use for dry-run validation, Terraform/Helm/Kustomize/Kubernetes apply after
confirmation, and rollout verification after apply.

Do not use for live troubleshooting, rollback investigation, cloud inspection,
authoring infra, pushing Docker images, triggering GitHub Actions workflows, or
applying without plan/diff evidence. Use `operating-infra` for inspection and
troubleshooting.

Dockerfiles and GitHub Actions are validate-only in this skill.

## Usage

`/deploying-infra --dry-run [environment] [scope]` validates only. `/deploying-infra --apply <environment> [scope]` validates, asks, applies, then verifies. `/deploying-infra --background --dry-run [environment] [scope]` starts background validation.

Rules:

- Default mode is `--dry-run`.
- `--background` is valid only with `--dry-run`.
- `--apply` always stops for confirmation after showing plan/diff evidence.
- Production confirmation must include the exact environment name.
- If environment, context, namespace, workspace, chart, release, path, or account is unclear, ask one question.

## Workflow

1. Parse mode, environment, and optional scope.
2. Detect infra with `Glob`, `Grep`, and `Read` before shell commands.
3. Classify detected types: apply-capable Terraform/Helm/Kustomize/Kubernetes; validate-only Dockerfile/GitHub Actions.
4. Check required CLIs with safe version or discovery commands.
5. Read `references/validation-checklists.md` and use only detected sections.
6. Run validation and inspect source-backed policy checks.
7. For apply-capable types, show plan/diff evidence.
8. Stop on `--dry-run`; ask and apply on `--apply`.
9. Verify changed resources after apply.

Use a background or delegated validation agent only for large scans or explicit
`--background`. The agent validates only; it must not apply changes.

## Validation and evidence

Every validation claim needs exact command output, `file:line`, or a skipped-check
reason. For apply-capable types, plan/diff evidence is mandatory before confirmation.
Use the reference checklist for commands. Do not run commands with unresolved
placeholders; ask first.

Before confirmation, show:

```markdown
## Pre-flight: READY | BLOCKED

### Scope

- Environment: <env>
- Type: <terraform|helm|kustomize|kubernetes>
- Context/account/namespace/workspace: <value>

### Plan or Diff Evidence

- `<command>` — <summary>

### Resources Affected

- Create: <count or unknown>
- Modify: <count or unknown>
- Delete: <count or unknown>

### Risks

- <destructive changes, security concerns, missing evidence, or none>
```

If validation is blocked, stop. Do not continue to confirmation.

## Confirmation and apply

Ask before every apply with options: apply now, review plan again, cancel. For
production, require the exact environment name. Cancel on ambiguous or mismatched
confirmation.

Allowed apply patterns only:

- `terraform apply tfplan`
- `helm upgrade --install <release> <chart> --values <values-file>`
- `kustomize build <overlay> | kubectl apply -f -`
- `kubectl apply -f <path>`

Use only commands already matched to the repo layout. Do not write deployment logs
unless the repo already documents that convention.

If apply fails, stop with `DEPLOYMENT FAILED`. Do not rollback without separate
confirmation.

## Verification

After apply, verify the changed resources with the relevant checklist command or
repo convention. If rollout times out or health is degraded, show investigation
and rollback options, then ask what to do next.

## Output contracts

Use the matching header, then the listed fields.

```text
DRY RUN COMPLETE
Status; Environment; Types; Validation; Plan/Diff; Blockers; Skipped

AWAITING CONFIRMATION
Environment; Type; Command; Destructive changes; Confirmation needed

BACKGROUND VALIDATION STARTED
Agent ID; Mode; Scope

DEPLOYMENT COMPLETE
Environment; Type; Status; Applied; Verification; Rollback option

DEPLOYMENT BLOCKED | DEPLOYMENT FAILED
Environment; Type; Reason; Evidence; Next step
```

## Failure handling

- Unknown target detail: ask one question.
- Missing tool, missing plan/diff evidence, unshown destructive change, or blocked validation: stop.
- Apply failure or partial deployment: report exact evidence and ask before rollback.
- Rollout timeout or degraded health: show rollback and investigation options, then ask.
- User cancels or gives ambiguous confirmation: stop cleanly.