skills.rest
gittower
gittowerOFFICIAL
Explore all skills by this author →
Website𝕏@gittowerGitHub

release

Update changelog and version files from git history using semantic versioning.

413|31|Updated Mar 16, 2025
Search Tags:#changelog#conventional commits#release#semantic versioning#git history#version bump
One-click install
npx skills add https://github.com/gittower/git-flow-next --skill release-gittower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/release
Command: npx skills add https://github.com/gittower/git-flow-next --skill release-gittower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort and guesswork from preparing a software release by analyzing git history, deciding the correct semantic version bump, and updating release files consistently.

Core Features & Use Cases

  • Version Bumping: Determines whether a release should be major, minor, or patch based on conventional commits and breaking changes.
  • Changelog Generation: Produces human-readable changelog entries grouped into the right sections for user-facing updates.
  • Release File Updates: Keeps CHANGELOG.md and version files in sync, handling both fresh releases and reruns after an incomplete release attempt.
  • Use Case: A maintainer can ask for a release update after a sprint, and the Skill will prepare the version, changelog, and commit message needed to publish it.

Quick Start

Ask the release skill to prepare the next version and changelog from the current git history.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a changelog from git history using semantic versioning?▼

The Skill generates a changelog from git history by comparing conventional commits since the latest tag, determining the semantic version bump, and producing human-readable changelog entries grouped by user-facing updates.

How does semantic versioning decide between a major, minor, or patch version bump?▼

The semantic versioning bump level is decided by analyzing conventional commit messages in git history, triggering major bumps for breaking changes, minor bumps for features, and patch bumps for fixes.

Can I update version files and CHANGELOG.md together for a software release?▼

Yes, the Skill updates version constants and CHANGELOG.md together consistently, keeping both release files perfectly in sync during the version bumping and changelog generation process.

What is the best way to prepare a software release after a development sprint?▼

The best way to prepare a software release is to analyze pending git history since the latest tag, automatically bump the version, generate the changelog, and prepare the commit message needed to publish.

Do I need conventional commits to automate my changelog generation?▼

Yes, conventional commits are required to automate changelog generation because the Skill relies on their structured format to group user-facing updates and correctly determine the semantic version bump.

Related Skills

Explore More Software Engineering Skills→
LllooogggLlloooggg
26

commit

Automate a gated git commit workflow with conventional messages and pre-commit checks.

Community
Advanced
tneztnez

release-package

Create and publish new npm package versions with changelog updates.

Community
Intermediate
t0labt0lab
2

git-conventional

Enforce Conventional Commits formatting and map commit types to semantic version bumps.

Official
Basic
jhlee0409jhlee0409
7

afc:launch

Generate CHANGELOG entries, README updates, and GitHub release notes from git history.

Community
Intermediate