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, 发布前检查, 是否可发布.

Jump to install Review files

Repository: Websoft9/docker-library
Last source activity: August 18, 2026 at 09:42
Detected SKILL.md language: English
Stars: 68
Forks: 36

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/Websoft9/docker-library/tree/main/skills/release-readiness-check.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/Websoft9/docker-library --skill release-readiness-check

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

3 files

SKILL.md

Source instructions · Read-only preview

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.

View on GitHub

Back to search Back to installation

app-update

Use when the user wants to implement an approved app update after assessment, update one app to a target version, adjust app files, run validation, and produce a short test report. Trigger phrases: update app, implement update, 升级应用, 更新应用, update <app> to <version>.

2026-09-29

new-app

Use when the user wants to add one new application package, create a new app from official deployment docs, or asks for a new app implementation workflow. Trigger phrases: new app, create app package, add app, 新应用, 新增应用.

2026-09-28

deploy-validation

Use when an app package has been created or changed and must be proven deployable. Runs structure/policy gates, docker compose deploy, reachability, and log checks, and returns validation evidence. Trigger phrases: run validation, deploy check, validate deployment, 部署验证, 验证应用.

2026-09-20

View all from this repository

release-readiness-check

Source facts

Install options

Install with an AI assistant

Review the source files

More from this repository

Install with an AI assistant

More from this repository