release

Cut a new release from the main branch with versioning, changelog generation, and git tagging.

438|11|Updated Nov 22, 2025

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

Ready to run

npx skills add https://github.com/ziggy42/epsilon --skill release-ziggy42

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams through cutting a release from the main branch, ensuring version accuracy, changelog generation, and proper git tagging, while enforcing a clean working tree prior to release.

Core Features & Use Cases

Version integrity: updates the project version and corresponding files consistently.
Changelog generation: drafts a user-facing changelog from commits since the last release.
Release automation: commits changes, creates a tag, and pushes to the main remote.
Use Case: Release managers can automate a routine release workflow from a single command, reducing human error and speeding up delivery.

Quick Start

Cut a new release from the main branch by updating the version, generating the changelog, and tagging the release.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate git tagging and changelog generation for a new release?▼

You can automate git tagging and changelog generation by cutting a new release from the main branch. This process updates your project version, drafts a user-facing changelog from recent commits, and pushes the new tag to the remote.

What is the best way to cut a clean release from the main branch?▼

The best way to cut a clean release is using an automated workflow that enforces a strict clean working tree prior to release. This ensures version integrity by consistently updating project files before committing changes and creating a git tag.

Does the release automation process require a clean working tree?▼

Yes, the release automation process strictly requires a clean working tree before cutting a release. Enforcing this guardrail prevents uncommitted changes from being included in the new version tag.

How does changelog generation work when cutting a software release?▼

Changelog generation works by automatically drafting a user-facing changelog from commits made since the last release. This ensures the CHANGELOG.md accurately reflects all updates when the new version is tagged.

Can I use this release workflow to update version files and push tags automatically?▼

Yes, you can use this release workflow to update specific version files like epsilon/version.go automatically. It commits these version changes, creates a git tag, and pushes everything to the main remote origin.

What precautions are enforced when cutting a release from main?▼

The main precaution enforced is verifying a clean working tree before starting the release process. This guardrail stops uncommitted or untracked files from accidentally being included in the tagged release commit.