What problem does it solve? After an epic is finished and merged, teams still need a disciplined way to cut a release: picking the right semver bump, promoting the accumulated CHANGELOG entries, creating an annotated git tag, and pushing it — all without accidentally publishing an unreviewed artifact. This Skill walks that release act step by step with a separate human approval gate for every mutating action. ## Core Features & Use Cases - Pre-release verification: Confirms clean tree, passing tests, and CI-green status on the last build-relevant commit via GitHub CLI before anything is tagged. - Semver determination and CHANGELOG promotion: Walks commits since the last tag to classify the bump, then renames ## [Unreleased] to the new version heading without rewriting accumulated entries. - Four separate approval gates: CHANGELOG commit, annotated tag creation, commit push, and tag push are each confirmed individually — never bundled — so nothing irreversible happens silently. - Use Case: An epic was just wrapped with aiwfx-wrap-epic and merged to main. You say "release v1.2" and the Skill verifies CI, proposes the version, updates CHANGELOG.md, and walks you through each gated commit, tag, and push. ## Quick Start Say "cut a release" or "tag release v1.2" after your epic is wrapped and merged, and approve each gate as it is presented.
