release

Name: release
Availability: InStock
Author: mikecubed

Calculate semver from conventional commits, update CHANGELOG, and tag the repository.

Updated Mar 18, 2026

Search Tags:#automation #git #changelog #release #semver #tagging

Ready to run

npx skills add https://github.com/mikecubed/agent-orchestration --skill release-mikecubed

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/flow/skills/release
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill release-mikecubed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release workflow for plugin and software repositories, ensuring consistent versioning, changelog discipline, and auditable release artifacts.

Core Features & Use Cases

Conventional-commit semver calculation to determine the next version and update changelog accordingly.
CHANGELOG.md updates with a new [version] section and grouped commits.
Git tag creation for the calculated or explicit version.
Optional GitHub release creation via gh when a token is available.
Durable release-summary.md artifact that records version, commits, tags, release status, and skipped steps.

Quick Start

Use the release skill to generate a new release from the current git history and emit a release-summary.md artifact.

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 from conventional commits?▼

Automate semantic versioning by calculating the next version directly from conventional commit history, updating the CHANGELOG.md with grouped commits, and tagging the repository. This workflow ensures consistent version bumping without manual calculation.

Can I override the calculated semver version during a git release?▼

Yes, you can override the calculated semver version during a git release by providing an explicit --version override. The workflow will use the specified version to update the CHANGELOG and create the git tag instead of deriving it from commit history.

Does the release workflow require the GitHub CLI to create a GitHub release?▼

The release workflow optionally creates a GitHub release via the gh CLI when a token is present. If the tooling is missing, it gracefully skips release creation while still completing the semver tag and CHANGELOG updates locally.

What happens if my git working tree is not clean before tagging?▼

The release workflow validates git history depth and ensures a clean working tree before proceeding. If the working tree is not clean, the process will halt to prevent tagging uncommitted changes and ensure a stable release artifact.

How do I generate an auditable release summary for my software repository?▼

Generate an auditable release summary by running the automated release workflow, which emits a durable release-summary.md file. This artifact records the version, commits, tags, release status, and any skipped steps for full traceability.

What is the best way to automate changelog generation and git tagging together?▼

The best way to automate changelog generation and git tagging is using a single workflow that parses conventional commits to determine semver, appends a new version section to CHANGELOG.md, and creates the corresponding git tag automatically.