Skill

releasing

Create a versioned release with semantic versioning

npx claudepluginhub jugrajsingh/skillgarden --plugin gitmastery

Tool Access

This skill is limited to using the following tools:

Bash(git *)Bash(pwd)ReadEditGlobAskUserQuestion

Preview

Start or finish a release with semantic versioning.

SKILL.md

Similar Skills

using-git-worktrees

169.2k

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

subagent-driven-development

169.2k

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

3 files

superpowers

dispatching-parallel-agents

169.2k

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitFeb 11, 2026

Actions

View Source View Plugin View on GitHub View README

Create Release

Start or finish a release with semantic versioning.

Usage

/gitmastery:release         # Analyze and suggest version
/gitmastery:release 1.3.0   # Specific version

Workflow

1. Analyze Commits

LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null)
echo "Last tag: $LAST_TAG"
git log $LAST_TAG..HEAD --oneline

2. Determine Version Bump

Pattern	Bump	Example
BREAKING or ! suffix	MAJOR	1.2.3 → 2.0.0
feat:	MINOR	1.2.3 → 1.3.0
fix:, perf:	PATCH	1.2.3 → 1.2.4

3. Present Options

AskUserQuestion:
  question: |
    Ready to create release?

    Current: v1.2.1
    Commits: 6 since last release

    Changes detected:
    - 2 feat: (new features)
    - 3 fix: (bug fixes)
    - 1 docs: (documentation)

    Suggested: 1.3.0 (MINOR)

  options:
    - "1.3.0 (Recommended)" - MINOR
    - "2.0.0" - MAJOR
    - "1.2.2" - PATCH

4. Start Release

git flow release start <version>

5. Update Version Files

Common files to update:

pyproject.toml: version = "<version>"
package.json: "version": "<version>"
CHANGELOG.md: Add version header

6. Finish Release

Use changelog content for tag message. Skip pre-commit hooks on the merge commit:

git flow finish --no-verify --tag -m "v<version>

## Added
- Feature 1
- Feature 2

## Fixed
- Bug fix 1"

Note: --no-verify skips pre-commit hooks on the merge commit. This is safe because the merge is mechanical — all code was already validated when committed to the release branch.

7. Push

git push origin main --tags
git push origin develop

Hotfix Flow

For urgent production fixes:

git checkout main
git flow hotfix start <name>
# ... fix ...
git flow finish --no-verify --tag

Stuck Merge State

If finish fails with "a merge is already in progress", clear the stale state file:

rm .git/gitflow/state/merge.json

Then retry. See /gitmastery:finish for details.