Verified:GitHub

release

Create tagged releases and changelogs from conventional commits on GitHub and GitLab.

11|7|Updated Nov 6, 2015

Search Tags:#git #changelog #conventional commits #github #release #gitlab

One-click install

npx skills add https://github.com/gufranco/dotfiles --skill release-gufranco

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/gufranco/dotfiles/tree/main/claude/skills/release
Command: npx skills add https://github.com/gufranco/dotfiles --skill release-gufranco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, glab, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of tagged releases and generates a changelog from conventional commits, streamlining your software release process.

Core Features & Use Cases

Automated Versioning: Determines the next semantic version based on commit types (feat, fix, breaking changes).
Changelog Generation: Compiles a human-readable changelog from commit messages.
Platform Support: Works with both GitHub and GitLab.
Use Case: After merging a new feature and several bug fixes into your main branch, use this Skill to automatically tag the release, generate a changelog detailing the new feature and fixes, and push it to your repository.

Quick Start

Use the release skill to create a new tagged release with an auto-generated changelog.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automatically generate a changelog from conventional commits?▼

Automatically generate a changelog from conventional commits by parsing commit messages to compile a human-readable summary of features, fixes, and breaking changes. This process categorizes your git history into a structured release log.

How do I automate semantic version bumps based on commit types?▼

Automate semantic version bumps by analyzing conventional commit types like feat, fix, and breaking changes. The system determines the next version number incrementally, applying major, minor, or patch bumps based on the parsed commit history.

Can I create tagged releases on both GitHub and GitLab?▼

Yes, you can create tagged releases on both GitHub and GitLab. The process requires the gh CLI for GitHub and glab CLI for GitLab to manage platform integration, push tags, and update repositories automatically.

What is the best way to preview a release before finalizing it?▼

The best way to preview a release before finalizing is to use a dry-run option. This allows you to preview the generated changelog and the calculated semantic version bump without pushing any tags or making permanent repository changes.

Do I need to install the gh and glab CLIs to manage git tags?▼

Yes, you need to install the gh and glab CLIs to manage git tags across platforms. These command-line interfaces provide the necessary platform integration to authenticate, push tags, and manage releases on GitHub and GitLab respectively.