What problem does it solve? Shipping a release involves many error-prone manual steps — verifying tests pass, reviewing unreleased changes, writing changelogs, bumping versions consistently, tagging, and publishing. This workflow coordinates the entire release lifecycle through a structured WHY/WHAT/HOW framework so nothing gets skipped. ## Core Features & Use Cases - Preflight Gates: Verifies tests pass, working tree is clean, documentation exists, no secrets are tracked, and CI is green before any release work begins. - Scoped Release Review: Reviews only commits since the last tag, detecting breaking changes and producing a semver recommendation (major/minor/patch). - Automated Changelog & Version Bump: Generates Keep-a-Changelog entries from git history and updates versions consistently across pyproject.toml, package.json, and Cargo.toml. - Use Case: You have 14 commits since v0.3.0 of your Python package. Run the workflow to get a preflight report, a review of unreleased changes, a generated CHANGELOG entry, a v0.4.0 tag, a GitHub Release, and a PyPI publish — with confirmation required before every irreversible step. ## Quick Start Ask the assistant to run the release-engineering workflow in ship mode on the current repository to preflight, version, tag, and publish the next release.
