release-readiness-check
Use when the user wants to know whether a task is ready for owner E2E, merge, or release, or asks for a final release gate summary. Trigger phrases: release readiness, ready to ship, 发布前检查, 是否可发布.
来源信息
- 仓库
- Websoft9/docker-library
- 最近来源活动
- 2026年8月18日 09:42
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 68
- Forks
- 36
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
3 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- release-readiness-check
- description
- Use when the user wants to know whether a task is ready for owner E2E, merge, or release, or asks for a final release gate summary. Trigger phrases: release readiness, ready to ship, 发布前检查, 是否可发布.
# Release Readiness Check
Assess whether one task is ready for owner E2E, merge, or release.
This skill follows `docs/ai-sdlc/05-quality-gates.md`, `docs/ai-sdlc/06-test-report-format.md`, and `docs/ai-sdlc/09-owner-e2e-runbook.md`.
Supporting files in this skill:
- `checklist.md`
- `report-template.md`
## Inputs
- app name or task scope (required)
- latest test report (required)
- latest issue or PR state (optional)
## Steps
1. Read the latest test report.
2. Check whether gates 0-3 are satisfied.
3. Identify any missing evidence.
4. Summarize owner E2E focus.
5. Output one readiness result.
## Output
- readiness: ready-for-e2e | blocked | not-enough-evidence
- blocking points
- owner focus
## Rules
- This is a gate review, not implementation.
- Do not mark ready when evidence is missing.
在 GitHub 查看