release

Automate versioned software releases with semantic versioning and GitHub CLI.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/kirvin/copilot-cli-essentials --skill release-kirvin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/kirvin/copilot-cli-essentials/tree/main/plugins/cpe/skills/release
Command: npx skills add https://github.com/kirvin/copilot-cli-essentials --skill release-kirvin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of cutting a new software version, ensuring consistency and reducing manual effort.

Core Features & Use Cases

  • Automated Versioning: Automatically determines and bumps the next semantic version (patch, minor, major).
  • Changelog Generation: Creates a detailed changelog based on git commit history, grouped by type (features, fixes, etc.).
  • Tagging and Publishing: Creates git tags and publishes a GitHub release with the generated changelog.
  • Use Case: After merging a new feature, use this skill to automatically prepare and publish a v1.1.0 release, including updating the CHANGELOG.md and creating a GitHub release.

Quick Start

Use the release skill to cut a patch release for the current project.

Frequently Asked Questions about 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 history?

You can automate semantic versioning and changelog generation by using a script that parses conventional commit messages from git history to determine the next version bump and groups commits by type to update the changelog automatically.

What's the best way to create a GitHub release with an auto-generated changelog?

Creating a GitHub release with an auto-generated changelog is done by integrating with the GitHub CLI, which uses your git tag and commit history to publish a structured release containing grouped features and fixes directly to the repository.

Does this release automation tool require conventional commit formats to work?

Yes, this release automation tool supports conventional commit formats to accurately categorize changelog entries and determine whether a patch, minor, or major semantic version bump is required for the release.

Can I cut a patch release for my current project without manually editing the version files?

You can cut a patch release without manually editing version files by running the release skill, which automatically bumps the semantic version, generates the changelog, creates a git tag, and publishes the GitHub release.

Why does automated changelog generation group commits by type like features and fixes?

Automated changelog generation groups commits by type such as features and fixes because it parses conventional commit history, ensuring the resulting changelog clearly categorizes changes for better readability and version tracking.