菜单
Start here to ship built-and-tested code to its target safely — release steps, rollout, smoke checks, and rollback.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
Start here to settle how a non-trivial change will be built — interfaces, contracts, file-level structure, and trade-offs.
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Start here to document what shipped — READMEs, API docs, ADRs, and usage — once a feature lands or an interface changes.
Start here to scout an unfamiliar problem space — research existing solutions, patterns, anti-patterns, constraints, and technical feasibility before committing to an approach.
| name | deployment |
| description | Start here to ship built-and-tested code to its target safely — release steps, rollout, smoke checks, and rollback. |
| context | fork |
| agent | release-engineer |
Ship it safely. Take built-and-tested code to its target environment with a path forward and a path back. Decide the version, run the release, confirm it works in place, and be ready to roll back the instant it doesn't.
A release is only done when a smoke check proves the deployed version is healthy. "It deployed" is not the same as "it works."
The version shipped, the rollout method used, the smoke-check result, and the exact rollback command for this release.
