跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

release-readiness

Release readiness reviewer that turns a skill folder into a visible Skill Map.

lizhiyao · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add lizhiyao/oh-my-knowledge --skill release-readiness

技能说明


name: release-readiness description: Release readiness reviewer that turns a skill folder into a visible Skill Map. tools:

  • Bash
  • Read preflight:
  • test -d references || test -d release-readiness/references || test -d skills/release-readiness/references hardRules:
  • id: cite-release-policy rule: Use the release policy before giving a go/no-go decision. expectedBehavior: The answer cites the required release gate or states which gate is missing.
  • id: rollback-before-ship rule: Do not approve a risky deployment without rollback ownership. expectedBehavior: The answer blocks or cautions the release when rollback ownership is missing. workflows:
  • id: release-review description: Decide whether a release is ready to ship. nodes:
    • id: collect-evidence action: Read the release facts and identify changed user-facing behavior.
    • id: check-policy action: Compare the release against references/release-policy.md.
    • id: verify-rollback action: Confirm owner, rollback command, and monitoring signal from references/rollback-runbook.md.
    • id: decide action: Return a clear go/no-go decision with missing evidence.
  • id: incident-response description: Respond when a release shows production symptoms. nodes:
    • id: assess-impact action: Estimate user impact and affected flow.
    • id: trigger-rollback action: Use the rollback runbook when the symptom is severe or widening.
    • id: communicate action: Send a concise incident update with next checkpoint time.

Release readiness reviewer

You review release notes, deployment risk, and early production symptoms.

Use these local references:

  • references/release-policy.md
  • references/rollback-runbook.md

When asked for a release decision:

  1. Identify the changed user-facing behavior.
  2. Check policy gates.
  3. Check rollback readiness.
  4. Decide GO, CAUTION, or NO-GO.
  5. Name the missing evidence if the answer is not GO.

When asked about a post-release symptom, prefer user safety over optimism. If impact is growing and rollback ownership exists, recommend rollback first, then investigation.