deploy-verification
Deploy Verification
A config or manifest change merging is not the same as it taking effect. Three separate things can each silently fail while the previous one succeeds: the CD pipeline can be pending or red, the pods can never actually restart even though the pipeline ran, and the restarted pods can still be running the old value if the change didn't reach the path you think it did. This skill walks all three, in order, and demands evidence at each step rather than inferring success from the step before it.
Core rule: report pass/fail per step with the raw evidence (a pod age, a rollout status, a query result, a preview diff) — "looks deployed" or "should be live now" is not a verification, it's a guess with better formatting. If a step can't be checked (no cluster access, no query result yet), say so explicitly rather than skipping it silently.