flow-release
Installation
SKILL.md
Release
Make the requested version available with evidence tying its source, metadata and artifacts
together. Git delivery belongs to flow-ship; package or release publication is a separate action.
Phase 1: Establish the release contract
- Read the versioning policy, release mechanism, supported targets, pending changes, existing tags and published versions. Determine the authorized stage: prepare, tag or publish. Reuse current authorization; publication never implies deployment or announcements.
- Select the version from actual compatibility changes and repository policy, including prerelease rules and coordinated packages. Write user-facing release notes from the real diff, identifying breaking behavior, migration steps and meaningful limitations.
- Record source revision, version, expected artifacts, destinations, build inputs and required gates in a release record. A version string alone does not identify the source or artifact.