release-readiness
把感性判断改为数据驱动的发布流程，降低夜间故障风险。
可能需访问生产指标与部署权限，注意权限控制。
基于证据生成可执行的 go/no-go 检查表、冒烟套件和分阶段发布策略。
帮你把“可以发版吗”从凭感觉变成有证据的决定。会输出可执行的 go/no-go 检查表、能在五分钟内跑完的 smoke 套件、分阶段发布的度量闸门和事先定义好的回滚标准，并给出部署后核验步骤。用在发版本前做最后把关，强调用数据而不是主观判断来放行。
▸ 展开 SKILL.md 英文原文
Validate release readiness with evidence-based go/no-go decisions. Covers go/no-go checklists, smoke test suite design, staged rollout validation, rollback criteria and procedures, and post-deployment verification. Ensures release confidence comes from data, not feelings. Use when: "release ready," "go/no-go," "smoke test," "release checklist," "rollback plan," "staged rollout," "canary deploy." Not for: safe-release techniques (flags, canary, dark launch) applied during the rollout itself — use testing-in-production; scheduled probes that run continuously after release — use synthetic-monitoring; designing new tests from prod telemetry — use observability-driven-testing. Related: testing-in-production, qa-metrics, ci-cd-integration, ai-system-testing.
帮我安装这个 skill：https://raw.githubusercontent.com/petrkindlmann/qa-skills/main/skills/release-readiness/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/petrkindlmann/qa-skills/main/skills/release-readiness/SKILL.md"<objective> "I think it's fine" ships the bug that the rollback you never practiced can't undo at 6 PM on a Friday. This skill turns "ready to ship" into something measurable: a go/no-go checklist with evidence for each item, a sub-5-minute smoke suite, a staged rollout with metric-gated promotion, rollback thresholds defined before deploy, and post-deployment verification. Every section gives concrete criteria, not aspirations. </objective> --- ## Discovery Questions Check `.agents/qa-project-context.md` first — if it exists, use it and skip anything answered there. Then ask only what's missing. **Release cadence and process:** - How often do you release, and who makes the go/no-go call