release

name	release
description	Create a release branch from dev with version bumps and changelog. Use when the user wants to prepare a new release, bump a version, or cut a release. Triggers on phrases like "release 17.1.2", "cut a release", "prepare a release", "version bump", or just "/release".

Release

Create a release branch from dev with version bumps and a structured changelog PR.

Arguments

The skill accepts an optional version argument (e.g., /release 17.1.2).

If no version is provided, read the current version from package.json and suggest the next patch version (increment the last number). Confirm with the user before proceeding.

Instructions

1. Pre-flight checks

Before anything else, verify the workspace is ready:

git fetch origin
git status          # must be clean — warn and stop if uncommitted changes
git checkout dev
git pull

Check that dev is not behind main:

git log dev..origin/main --oneline

If main has commits not in dev, warn the user — they may need to merge main into dev first.

2. Determine the version

• If a version argument is provided, use it
• Otherwise, read package.json version, increment the patch number, and confirm with the user

3. Create the release branch

git checkout -b release/<version>

Branch naming convention: release/X.Y.Z (e.g., release/17.1.2)

4. Update version in these files

All files must be updated — the old version appears in each: