deploy-preflightlisted

Read-only deployment pre-flight scan — repo state, secrets sync check, deploy-changes diff, migration verify locally. Reports what WOULD break a deploy without committing to one. Use when the user says '/deploy-preflight', 'check the deploy', 'what would deploy break', 'preflight', or wants to validate readiness before running /deploy.
Maximumsoft-Co-LTD/claude-flightdeck · ★ 2 · AI & Automation · score 78

Install: claude install-skill Maximumsoft-Co-LTD/claude-flightdeck

# /deploy-preflight — Read-Only Deploy Risk Scan The split-off of `/deploy` Phase 1. **No environment risk** — does not sync, does not commit, does not mutate any cluster state. Outputs a risk report so a human can decide whether to proceed to `/deploy`. ## When to run - Before announcing a deploy slot to the team. - After a sprint promotion, before bumping the meta submodule pointer. - Any time you want a confidence check without holding the deploy slot. Sister skill: `/deploy` (drives the full 5-phase orchestration). ## Token budget (MANDATORY) - Pure read + Grep. No Write. No mutation. - Reuses the same references as `/deploy` — load lazily as you encounter each sub-step. ## Input `/deploy-preflight <environment>` Environment is required (the secrets / cluster state differs per env). ## Variant router Same routing as `/deploy` Phase 1. Load when you reach each sub-step: | If the project uses... | Load before... | |---|---| | External Secrets Operator (ESO) | Step 4 — `../deploy/references/secrets-externalsecrets.md` | | Sealed-secrets (Bitnami) | Step 4 — `../deploy/references/secrets-sealedsecrets.md` | | Any DB schema change in scope | Step 5 — `../deploy/references/migrations-patterns.md` | | Always (to know the smoke-gate criteria) | Step 6 — `../deploy/references/health-probes.md` | ## Steps ### 1. Confirm cluster context ```bash kubectl config current-context # is this the TARGET env? ``` If it's not the target environment, switch BEFORE conti