git-release

Automate GitHub/GitLab releases by analyzing commits and updating CHANGELOG.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the entire process of releasing new versions of your software on GitHub or GitLab, from analyzing commits to creating tagged releases.

Core Features & Use Cases

  • Automated Changelog Generation: Analyzes Git commit history to automatically update your CHANGELOG.md file based on Conventional Commits.
  • Semantic Versioning: Determines the appropriate next version number (MAJOR, MINOR, PATCH) based on the type of changes introduced.
  • Release Creation: Creates Git tags, pushes them to the remote, and generates formatted release notes on GitHub or GitLab.
  • Use Case: After merging a new feature and several bug fixes, you can trigger this Skill to automatically prepare and publish a new release, including updating the changelog and creating a release tag.

Quick Start

Use the git-release skill to automate the creation of a new version release.

Frequently Asked Questions about git-release

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

FAQPage Schema
How do I automate GitHub releases from conventional commits?

Automate GitHub releases by parsing conventional commits to determine semantic versioning, update CHANGELOG.md, and create tagged releases via the gh CLI.

How do I generate a changelog automatically from Git commits?

Generate a changelog automatically by analyzing your Git commit history and updating CHANGELOG.md based on the Conventional Commits formatting standard.

Can I use this to automate GitLab release creation?

Yes, you can automate GitLab release creation by integrating with the glab CLI to push tags and generate formatted release notes directly on GitLab.

How does semantic versioning work when automating Git releases?

Semantic versioning determines the next version number by analyzing commit history, bumping MAJOR, MINOR, or PATCH versions based on the specific types of changes introduced.

Do I need specific CLIs installed to push Git tags and releases?

Yes, you need the gh or glab CLIs installed to create Git tags, push them to the remote, and generate formatted release notes on GitHub or GitLab.

What is the best way to prepare a software release after merging features?

Prepare a software release after merging features by triggering an automated workflow that analyzes commits, updates the changelog, determines the version, and publishes the release.