com um clique
release-readiness
// Use before final merge recommendations or version tag release candidates to verify quality gates and SemVer decisions.
// Use before final merge recommendations or version tag release candidates to verify quality gates and SemVer decisions.
Use when evaluating public API impact, checkKotlinAbi/updateKotlinAbi expectations, SemVer implications, and ADR-005 response-shape compliance.
Use when local or CI checks fail to quickly classify root cause and apply a minimal safe fix.
Use when behavior, protocol, architecture, API, or workflow changed and docs must be synchronized with minimal drift.
Use for any change affecting wire framing, handshake, transport semantics, session behavior, or protocol mapping.
Use when implementing a new transport module or making non-trivial transport behavior changes without violating module and engine architecture.
| name | release-readiness |
| description | Use before final merge recommendations or version tag release candidates to verify quality gates and SemVer decisions. |
Use this skill before final merge recommendations or version tag release candidates.