git-release

Automate Git release workflows with version bumps, changelogs, tags, and GitHub Releases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the end-to-end Git release workflow to ensure consistent versioning and GitHub releases across repositories.

Core Features & Use Cases

  • Bump semantic versions automatically based on changes
  • Generate changelogs from commits since last release
  • Create annotated git tags and publish GitHub Release
  • Suitable for teams enforcing release discipline across CI/CD pipelines

Quick Start

Provide the next release version and run the automation to bump the version, generate a changelog, tag, and publish a GitHub 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 semantic version bumping and GitHub releases?

To automate semantic version bumping and GitHub releases, you provide the next release version to bump the version, update the changelog, tag the commit, and publish the GitHub Release automatically.

What is the best way to generate a changelog from commits for a Git release?

Generating a changelog from commits for a Git release is handled automatically by analyzing repository changes since the last release, ensuring consistent versioning and release notes across your repositories.

Do I need the gh CLI and GITHUB_TOKEN to automate Git release workflows?

Yes, automating Git release workflows requires the git and gh CLI tools, proper repository permissions, and a valid GITHUB_TOKEN to create releases and interact with GitHub successfully.

Can I use this semantic release automation across different Git repositories?

Yes, you can use this semantic release automation across common Git repository scenarios by providing configurable repository identifiers and credentials to ensure consistent release discipline.

How does this approach compare to other tools for enforcing release discipline in CI/CD pipelines?

Unlike other tools, this approach combines semantic version bumping, changelog generation, and GitHub Release publishing into a single end-to-end workflow suitable for enforcing release discipline across CI/CD pipelines.