git-release

Automate semantic versioning and changelog generation from Git commit history.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/kunallimaye/lib-agents --skill git-release-kunallimaye
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-release
Source: https://github.com/kunallimaye/lib-agents/tree/main/skills/git-release
Command: npx skills add https://github.com/kunallimaye/lib-agents --skill git-release-kunallimaye

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating software releases by automating versioning and changelog generation based on commit history, ensuring consistency and reducing manual effort.

Core Features & Use Cases

  • Automated Versioning: Determines the next semantic version (MAJOR.MINOR.PATCH) based on commit types (feat, fix, BREAKING CHANGE).
  • Changelog Generation: Drafts release notes by summarizing changes from merged pull requests and commits.
  • Release Command Assistance: Provides a ready-to-use gh release create command.
  • Use Case: Before deploying a new version of your application, use this skill to automatically calculate the correct version number and generate a detailed changelog from your Git history.

Quick Start

Use the git-release skill to prepare the next release based on your commit history.

Frequently Asked Questions about git-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 git conventional commits?

Automate semantic versioning and changelog generation by analyzing conventional commit history to determine MAJOR.MINOR.PATCH increments and summarizing merged pull requests. This process calculates the correct version number and drafts release notes automatically.

How does semantic version determination work with conventional commit types like feat, fix, and BREAKING CHANGE?

Semantic version determination works by mapping conventional commit types to version increments: feat triggers a MINOR bump, fix triggers a PATCH bump, and BREAKING CHANGE triggers a MAJOR bump. This ensures releases adhere strictly to MAJOR.MINOR.PATCH versioning rules.

Can I generate a ready-to-use GitHub release command for my tagged releases?

Yes, you can generate a ready-to-use `gh release create` command for tagged releases. The process drafts release notes and facilitates version determination, providing the exact command syntax needed to publish the release on GitHub.

Does this release automation process support pre-release conventions for semantic versioning?

Yes, this release automation process supports pre-release conventions alongside standard MAJOR.MINOR.PATCH versioning rules. It calculates the appropriate pre-release version labels based on your commit history before drafting the final release notes.

What is the best way to calculate the next software version from a Git commit history?

The best way to calculate the next software version from Git commit history is to use conventional commit standards to automate the process. This ensures consistent version determination by summarizing merged pull requests and applying semantic versioning rules automatically.

Why use conventional commits for automating software release notes and version bumps?

Using conventional commits for automating software release notes and version bumps streamlines deployment preparation by ensuring consistency and reducing manual effort. It maps specific commit types directly to semantic version increments and changelog entries.