What problem does it solve?
Create reliable, auditable releases from a repository's current branch state without guessing the correct version, losing changelog history, or accidentally publishing unverified changes. The workflow reduces human error by analyzing commits, recommending semver bumps, drafting changelogs, and staging only release artifacts for commit and tag.
Core Features & Use Cases
- Analyze commit history (excluding merge and bot noise) and detect BREAKING CHANGE signals.
- Recommend SemVer bumps with explicit rationale and show current -> proposed version.
- Draft Keep-a-Changelog style entries rewritten for end users and prepend them to CHANGELOG.md.
- Run verification gates (tests, lint/typecheck/build) and require fresh evidence before releasing.
- Create release commit and annotated tag, optionally push refs and create a GitHub release after explicit confirmation.
- Use case: prepare a stable patch, minor, or major release from main or a release branch while preserving changelog integrity and auditability.
Quick Start
Run a dry-run release analysis, review the proposed version bump and changelog preview, then confirm to create the release commit and tag.