release

Name: release
Availability: InStock
Author: innomikitakutas

Automates GitHub releases, changelogs, and version tags from commit history.

Updated May 29, 2026

Search Tags:#automation #changelog #versioning #github #release

Ready to run

npx skills add https://github.com/InnoMikitaKutas/accelerator-test-task --skill release-innomikitakutas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/InnoMikitaKutas/accelerator-test-task/tree/main/.claude/skills/release
Command: npx skills add https://github.com/InnoMikitaKutas/accelerator-test-task --skill release-innomikitakutas

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of creating GitHub releases, generating changelogs, and tagging versions, saving developers time and reducing manual errors.

Core Features & Use Cases

Automated Release Creation: Generate GitHub releases with a single command.
Changelog Generation: Automatically create and update CHANGELOG.md with commit changes.
Version Tagging: Automatically tag versions based on commit history.
Use Case: After a new feature is added to your project, use this Skill to create a new release, generate a changelog, and tag the version.

Quick Start

Use the release skill to create a new release for your project.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate GitHub release creation from git commit history?▼

Automating GitHub release creation from git commit history is achieved by parsing commits to automatically generate releases, tag versions, and populate changelogs using semantic versioning and the Keep a Changelog format.

Can I automatically generate a changelog and update CHANGELOG.md using GitHub CLI?▼

Yes, you can automatically generate a changelog and update CHANGELOG.md using GitHub CLI by parsing git commit history to extract changes and format them according to the Keep a Changelog standard.

Do I need git and GitHub CLI installed to tag versions and generate changelogs?▼

Yes, you need both git and GitHub CLI installed to tag versions and generate changelogs, as these dependencies are required to interact with GitHub repositories and read local commit history.

What is the best way to manage semantic versioning tags for new project features?▼

The best way to manage semantic versioning tags for new project features is to automate version tagging based on git commit history, ensuring consistent release creation and accurate changelog generation.

How does semantic versioning work with automated changelog generation?▼

Semantic versioning works with automated changelog generation by analyzing git commit history to determine version bumps and categorizing changes into the Keep a Changelog format within CHANGELOG.md.

Why does my automated release creation require the Keep a Changelog format?▼

Automated release creation requires the Keep a Changelog format to ensure generated changelogs maintain a standardized, human-readable structure for documenting git commit changes across version tags.