ac-git-release

Release Command

Full release workflow: validate changelog, prepare a squashed release commit and tag, sync the VERSION file plus repo/package version metadata, rebase, push, and merge to main.

No arguments required - auto-detect the current branch, release version, and release inputs.

Compatibility Note

This pi wrapper preserves the original release workflow but performs the former milestone-preparation steps directly because ac-tools-milestone does not ship as a separate pi wrapper in the current package surface.

Context Awareness

Before any destructive history rewrite, use /skill:ac-git-git-safe to inspect the dry-run plan and confirm the exact squash/tag steps you intend to execute.

Phase 1: Prepare the Release Locally

1.1 Pre-Flight

Verify all of the following before rewriting history:

• git state is clean
• branch is not main
• commits exist ahead of origin/main
• CHANGELOG.md has a populated [Unreleased] section
• the next release version can be derived from VERSION or the latest v*.*.* tag

Suggested checks:

git status --short
git fetch origin main
git rev-parse --abbrev-ref HEAD
git log --oneline origin/main..HEAD
git tag -l 'v*.*.*' | sort -V | tail -1
test -f VERSION && cat VERSION
test -f CHANGELOG.md && sed -n '/\[Unreleased\]/,/^## /p' CHANGELOG.md

1.2 Determine Release Inputs

Capture these values for the rest of the flow:

• BRANCH: current branch name
• VERSION: next release tag (prefer patch bump from VERSION, otherwise patch bump from latest semantic tag)
• COMMITS_INCLUDED: the commit list that will be squashed

1.3 Prepare the Squashed Release Commit

Use the same dry-run-first safety rules as ac-git-git-safe:

1. propose the exact squash plan before executing
2. create a backup branch before rewriting history
3. squash the commits ahead of origin/main into one conventional commit
4. keep CHANGELOG.md aligned with the release contents
5. create an annotated tag for {VERSION} on the squashed commit
6. do not push yet