Verified:GitHub

release

Create GitHub releases with auto-generated changelogs from conventional commits.

2|Updated Jan 22, 2026

Search Tags:#conventional commits #github #semantic versioning #release automation #changelog generation #release tagging

Ready to run

npx skills add https://github.com/abnegate/claudes --skill release-abnegate

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the time-consuming work of manually determining a version bump and writing release notes by generating an appropriate changelog from commits and creating a GitHub release consistently.

Core Features & Use Cases

Auto-detect version bumps from commit history: Determines whether the next release should be major, minor, or patch based on commit messages and breaking-change signals.
Build categorized changelogs from conventional commits: Groups commits into breaking changes, features, fixes, and other changes, then formats them into a release-ready Markdown body.
Supports explicit versions and pre-releases: Accepts a semver value (optionally containing alpha/beta/rc markers) or bump keywords, and creates prereleases when requested or inferred.
Use case: When you merge multiple PRs and want a polished GitHub release quickly, this skill compiles the exact commit summary since the last tag and publishes it to the correct branch.

Quick Start

Ask: "release 1.2.3 on main with the changelog generated from commits since the last release".

Frequently Asked Questions about release

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

FAQPage Schema

How do I auto-generate a changelog from conventional commits for a GitHub release?▼

To auto-generate a changelog from conventional commits for a GitHub release, this skill analyzes commit history since the latest tag, groups changes into categories like features and fixes, and formats them into release-ready Markdown before publishing.

How do I determine the correct semantic versioning bump from commit history?▼

Determining the correct semantic versioning bump from commit history is done by analyzing conventional commit messages and breaking-change signals to infer whether the next release should be major, minor, or patch automatically.

Can I create a GitHub prerelease with an explicit semver value?▼

Yes, you can create a GitHub prerelease by providing an explicit semver value with alpha, beta, or rc markers, or by using bump keywords that the system evaluates to flag the release as a prerelease.

What is the best way to cut a new release from a specific branch using commit history?▼

The best way to cut a new release from a specific branch using commit history is to target the branch, analyze commits since the latest release tag, generate a categorized changelog, and use the GitHub CLI to create the release after user confirmation.

Does this release automation tool require manual confirmation before publishing?▼

Yes, this release automation tool requires explicit user confirmation before executing the GitHub release creation command, ensuring you review the inferred version bump and generated changelog prior to publishing.

Are categorized release notes grouped by conventional commit types supported?▼

Categorized release notes grouped by conventional commit types are fully supported, organizing commit history into breaking changes, features, fixes, and other changes to produce a structured Markdown body.