What problem does it solve? Cutting a release by hand involves resolving the current version from tags, computing the next semantic version, running git flow release start/finish, and pushing master, develop, and the tag — a multi-step process where mistakes leave the repository in a broken state. This Skill drives that entire flow end-to-end with strict preconditions and clear abort behavior. ## Core Features & Use Cases - Automated version resolution: Reads the latest tag on master, strips legacy v prefixes, and computes the next version with major, minor, or patch bumps (minor by default). - Full gitflow release lifecycle: Runs git flow release start and finish with non-interactive flags, then pushes master, develop, and the new tag as three separate pushes for clear failure attribution. - Hard precondition checks: Aborts on dirty working trees, missing git-flow AVH, non-fast-forward branches, existing release branches, or duplicate tags, and reports exact command output. - Use Case: A maintainer says "release 1.4.0" — the Skill verifies the repo state, creates release/1.4.0, finishes it with an annotated tag, pushes all refs, and prints a compact summary of the before/after SHAs. ## Quick Start Ask the assistant to cut a new release, for example by saying "cut a release with a patch bump" or "release version 2.0.0".