What problem does it solve? Maintaining long-lived release branches, promoting versions, and verifying native release artifacts involves many error-prone steps where a wrong branch mutation or premature publication can break the release line. This Skill encodes the branch policy, promotion gates, and verification procedures so release work stays consistent and auditable. ## Core Features & Use Cases - Long-lived branch policy enforcement: Keeps main as the active v5 line and v4 as a maintenance line anchored at a specific commit, with rules against force-pushing or repointing long-lived branches. - Release verification guidance: Directs archive, installer, upgrade, bootstrap, and publication work through the native release verification guide, including cargo-dist manifest ownership and multi-platform alpha checks. - Authorization boundaries: Treats tags, GitHub Releases, npm publishing, and dist-tags as separate operations requiring explicit authorization, never assumed. - Use Case: When preparing a v5.0.0-alpha release, use this Skill to confirm all four native verifiers pass on the reviewed commit, verify the draft-to-published GitHub release attestation, and only then update README installation instructions. ## Quick Start Ask the agent to prepare the tmux-team v5 prerelease readiness check following the release verification guide before any publication step.