deploying-infra

# 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...