菜单
Verify release readiness and post-release health from PRs, CI, tags, deploy evidence, rollback notes, and operator artifacts. Use when the user asks whether a release can ship, has shipped, or is safe to promote.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when changing Maestro runtime, hosted runner, event contracts, migration packaging, or internal-to-public mirror behavior.
Triage production incidents by building a timeline, scoping blast radius, identifying mitigations, and preserving evidence. Use when the user asks about an outage, regression, alert, Sentry issue, or incident follow-up.
Install automated Maestro code review in a GitHub repository's CI — add a pull_request workflow that runs `maestro exec` and posts a merge-readiness review as a PR comment. Use when the user wants to set up automated PR review, wire Maestro into CI/CD, or "install code review".
Correctness-first, depth-first security audit of a single repository using STRIDE, OWASP Top 10, the OWASP LLM Top 10, and supply-chain analysis. Use when the user asks for a security review, a vulnerability audit, a threat model, or a pre-release security pass.
Review GitHub pull requests for correctness, regressions, missing tests, and merge readiness. Use when the user asks for PR review, review feedback, or a pre-merge risk pass.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
| name | release-verification |
| description | Verify release readiness and post-release health from PRs, CI, tags, deploy evidence, rollback notes, and operator artifacts. Use when the user asks whether a release can ship, has shipped, or is safe to promote. |
| license | Complete terms in LICENSE.txt |
| compatibility | Maestro skill packages with bounded GitHub MCP tools and executable toolbox entries. |
| allowed-tools | ["read","search","bash"] |
| builtin-tools | ["read","search"] |
| mode | ship |
| isolatedContext | true |
| metadata | {"version":"0.1.0","category":"evalops-operations","artifactSchema":"evalops.maestro.skill.release_verification.v1"} |
Use this skill to prove release state from artifacts, not from branch vibes.
reference/checklist.md when the release has deploy, migration, or customer-visible risk.Run toolbox/release-readiness to emit the required release-verification report skeleton.
The bundled GitHub MCP config is limited to release, workflow, pull request, and check metadata. Use platform or deploy-specific tools only when the runtime grants them separately.