release

Automate semantic versioning, changelog generation, and Git tagging for releases.

1|1|Updated Mar 1, 2026

Search Tags:#git #changelog #versioning #release #git-cliff #commitizen

Ready to run

npx skills add https://github.com/heltondoria/claude-code-sdd-kit --skill release-heltondoria

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/heltondoria/claude-code-sdd-kit/tree/main/global/skills/release
Command: npx skills add https://github.com/heltondoria/claude-code-sdd-kit --skill release-heltondoria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the complex and error-prone process of version bumping, changelog generation, and tagging for software releases, ensuring consistency and saving development time.

Core Features & Use Cases

Automated Version Bumping: Intelligently determines the next semantic version based on commit history or explicit flags.
Changelog Generation: Creates a comprehensive CHANGELOG.md using git-cliff or falls back to commitizen's built-in functionality.
Git Tagging & Pushing: Creates annotated Git tags and pushes commits and tags to the remote repository.
Use Case: After merging a new feature and several bug fixes, run this Skill to automatically update the version, generate the release notes, tag the commit, and push everything to GitHub.

Quick Start

Run the release skill to automatically determine the next version, update the changelog, and create a git tag.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate semantic versioning and changelog generation from commit history?▼

Automate semantic versioning and changelog generation by analyzing commit history with commitizen to determine version bumps and git-cliff to create a comprehensive changelog. This ensures version numbers and release notes stay consistent across pyproject.toml or package.json and Git history.

Does git-cliff work with both pyproject.toml and package.json for release versioning?▼

Git-cliff works with both pyproject.toml and package.json for release versioning. The Skill manages version bumps directly within these configuration files, ensuring your semantic version updates align with your project's specific package manager and Git history.

What is the best way to create annotated Git tags and push releases automatically?▼

The best way to create annotated Git tags and push releases automatically is by using a workflow that performs pre-flight checks, generates changelogs with git-cliff, creates the tag, and handles push confirmations to ensure commits and tags sync to the remote repository safely.

How do I determine the next semantic version based on commit history?▼

Determine the next semantic version by parsing commit history with commitizen, which intelligently identifies whether a major, minor, or patch bump is required based on your conventional commit messages and explicit flags.

Can I run a dry-run for Git tagging and version bumping before pushing?▼

Yes, you can run a dry-run for Git tagging and version bumping before pushing. The workflow handles dry-runs and pre-flight checks, allowing you to verify changelog generation and version updates without making permanent changes to the remote repository.

Why should I use commitizen for automated version bumps instead of manual tagging?▼

Using commitizen for automated version bumps prevents human error and ensures consistency, unlike manual tagging. It intelligently calculates the correct semantic version from your commit history and synchronizes updates across your changelog, configuration files, and Git tags.