What problem does it solve? Closing out a multi-component release involves scattered manual steps: confirming every component merged, reviewing changes, writing the CHANGELOG, running readiness checks, and deciding when it is safe to ship. This Skill drives that entire wrap-up against the shared Marshall store so findings, review state, and readiness are consistent across machines, people, and agents. ## Core Features & Use Cases - Store-driven wrap workflow: Confirms all components are merged, composes change-review and readiness review skills, and reads their findings from the Marshall store instead of local state files. - Generated CHANGELOG with mode-aware handling: Fills the CHANGELOG from store-emitted sections, stamping the date in deploy mode or leaving it undated in tag mode, and derives UPGRADING notes from component breaking flags. - Hard high-severity gate: Refuses to hand off while any high-severity finding is open or deferred, then hands off to the deploy skill as ready-for-deploy or ready-to-ship. - Use Case: After all components of release 2.4.0 are merged, invoke the wrap to run per-component change reviews, fill the CHANGELOG in one commit, resolve readiness findings, and hand off a gated, ready-to-ship release. ## Quick Start Tell the agent to run /release-wrap to finish the release once all components are merged.
