菜单
Assess whether a build is ready to deploy or promote. Use when DevOps must verify release candidates, artifact provenance, test evidence, dependency/security gates, environment config, migration and rollback readiness, observability, and approval status before staging or production deployment.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Standardized backend implementation guidance for BE Dev using the SRS-declared Backend-Track and Backend-Framework. Use when coding, refactoring, or reviewing backend web APIs, BFFs, microservices, workers, jobs, or service integrations in TypeScript with Express, TypeScript with NestJS, Python with FastAPI, Java with Spring Boot, .NET Core C#, Pure Golang, Java Core, Golang with Gin, Golang with Fiber, Golang with Echo, or Golang with Kratos; BE Dev reads docs/SRS.md Backend-Track and Backend-Framework plus §3.4.5 Source Layout, then selects the matching reference so routing, layering, contracts, validation, observability, errors, transactions, and tests match the chosen stack.
How DevOps composes the local Docker environment for QA and operator trials, including port probing, secret-safe env discovery, test-only runtime-reset endpoint verification for direct-DB fixtures, QA deploy-report fields, and human trial URLs without editing project Compose files.
Concrete how-to for QA-Author writing Playwright specs from markdown TCs — project layout, full-state resets for direct-DB fixtures and caches, parallel-worker isolation, contract-aware URL assertions, network mocking, retries, traces, and visual diffs. Consult after `ui-test-execution` when the target surface is web AND the project uses Playwright.
QA-Exec run contract for executing authored test cases against the deployed build. Use when QA-Exec is dispatched for a task in-test to gather by-us/by-task test cases, check executable specs and instrumentation coverage, invoke the proper runner, execute UI tiers, validate visual specs, route failures, and write docs/qa-reports/<task-id>.md plus artifacts.
Codex-native orchestration entrypoint for Evo Talos. Use when the user asks for /sdlc-loop, sdlc-loop, start project, continue the SDLC loop, run the governed workflow, or auto-dispatch eligible SDLC work until the next gate. Acts as the Codex equivalent of the Claude slash command.
Framework-agnostic principles for executing UI tests against the running build — TC-to-spec mapping, selectors, full-state fixture reset across DB/cache/worker state, shared-resource parallelism, determinism, and visual diffs. Consult when QA-Author writes executable specs or QA-Exec invokes a runner against a deployed build.
| name | release-readiness |
| description | Assess whether a build is ready to deploy or promote. Use when DevOps must verify release candidates, artifact provenance, test evidence, dependency/security gates, environment config, migration and rollback readiness, observability, and approval status before staging or production deployment. |
| agents | ["devops"] |
| sdlc_phase | deploy |
| owner | Platform Eng |
| status | active |
Use this skill before any shared-environment deployment, release candidate promotion, or production change proposal. The goal is not to deploy; it is to decide whether deployment is safe to attempt.
docs/devops/<task-id>/release-readiness.md or equivalent report content.migration-safety, rollback-readiness, secrets-config-audit, and observability-readiness when applicable.ready, ready-with-warnings, or blocked. A warning must be non-critical and have an owner; a blocker prevents deployment.ready verdict.../migration-safety/SKILL.md - migration gate.../rollback-readiness/SKILL.md - rollback gate.../secrets-config-audit/SKILL.md - secret/config gate.../observability-readiness/SKILL.md - telemetry gate.../qa-execution-runner/SKILL.md - QA evidence consumed by readiness.