bump-version

name	bump-version
description	This skill should be used when the user asks to "bump version", "release a new version", "bump the version", "prepare a release", "update version numbers", "what version should this be", or mentions version bumping, semver analysis, or release preparation.
version	0.1.0

Bump Version

Analyze changes since the last version tag, determine the correct semver bump, and update all version references in the codebase.

Workflow

Step 1: Identify the Latest Version Tag

git tag --sort=-v:refname | head -1

The tag format is vMAJOR.MINOR.PATCH (e.g. v2.1.1).

Step 2: Analyze Changes Since the Last Tag

Gather the commit log and diff since the tag:

git log <tag>..HEAD --oneline
git diff <tag>..HEAD --stat

Step 3: Classify the Semver Bump

Apply Semantic Versioning rules to the changes:

Bump	Criteria
patch	Bug fixes, dependency bumps, formatting, docs, refactors with no behavioral change
minor	New features, new functions, new chain/token support, non-breaking additions
major	Breaking changes: renamed/removed public functions, changed function signatures, schema moves