Release

Derive version bumps, changelogs, and git tags from commit history.

Updated Apr 13, 2026

Search Tags:#automation #changelog #versioning #release #semver #git-tag #calver

Ready to run

npx skills add https://github.com/nille/shipkit --skill release-nille

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Release
Source: https://github.com/nille/shipkit/tree/main/shipkit/core/skills/release
Command: npx skills add https://github.com/nille/shipkit --skill release-nille

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the release workflow by deriving version bumps, changelogs, and git tags from commit history.

Core Features & Use Cases

Changelog generation from commit messages since last tag.
Automatic version bumping using SemVer or CalVer.
Git tagging and optional dry-run preview before publishing.

Quick Start

Prepare the next release by analyzing commits since the last tag, generating a changelog, bumping the version, and tagging.

Frequently Asked Questions about Release

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

FAQPage Schema

How do I automate version bumping and changelog generation from commit history?▼

Automate version bumping and changelog generation by analyzing commit messages since the last git tag to derive semantic or calendar version bumps and produce a formatted changelog automatically.

How does automatic release management work with SemVer and CalVer schemes?▼

Automatic release management works with SemVer and CalVer by assessing commit history since the last tag to determine the appropriate version increment, generating a changelog, and creating the corresponding git tag.

Can I generate a changelog and preview a release with a dry-run before creating a git tag?▼

Yes, you can preview a release with a dry-run before creating a git tag, allowing you to review the derived version bump and generated changelog without pushing any changes to your repository.

Does automated release tagging support multi-package repositories?▼

Automated release tagging supports multi-package repositories by analyzing commit history across the project to coordinate version bumps and changelog generation for the entire workspace.

What is the best way to assess release readiness from git commit history?▼

Assess release readiness from git commit history by analyzing commits since the last release tag to determine if the changes warrant a patch, minor, or major version bump under SemVer or CalVer rules.

Why should I use commit history for automated git tagging instead of manual versioning?▼

Using commit history for automated git tagging eliminates manual versioning errors by consistently deriving version bumps and changelogs directly from commit messages, ensuring release artifacts match actual code changes.