release

Automate version bumping, changelog generation, and GitHub release publishing for git projects.

Updated Apr 12, 2026

Search Tags:#automation #workflow #changelog #github #release #semver

Ready to run

npx skills add https://github.com/olivermorgan2/workflow-generator --skill release-olivermorgan2

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the friction and inconsistency of manual release ceremonies by automating versioning, changelog generation, tagging, and GitHub release publishing in a single, gated workflow.

Core Features & Use Cases

Automated Release Orchestration: Coordinates version bumping, changelog generation, git tagging, and GitHub release creation.
Project-Shape Awareness: Automatically detects if a project is a software product or a documentation/research workflow, adjusting the release framing and clarifier banners accordingly.
Safety Gates: Provides a dry-run mode and an explicit approval gate to ensure no mutations occur without user verification.

Quick Start

Invoke the release skill to automatically detect the next version and publish a 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 GitHub releases and changelog generation for git-based projects?▼

You can automate GitHub releases by orchestrating version bumping, changelog generation, and git tag creation in a single workflow. This coordinates the end-to-end release lifecycle to ensure semver compliance and secure repository mutations.

How does automated semver version bumping work for different repository types?▼

Automated semver bumping works by detecting project shape, distinguishing between software products and documentation or research workflows. It automatically determines the next version and adjusts the release framing and clarifier banners accordingly.

Can I preview a semver release before mutating git tags and publishing to GitHub?▼

Yes, you can preview a semver release using the built-in dry-run mode. This safety gate ensures no mutations occur to git tags or GitHub releases without explicit user verification and approval.

Do I need the gh CLI and git installed to orchestrate semver release workflows?▼

Yes, you need both the gh CLI and git installed to orchestrate semver release workflows. These dependencies are required to execute secure, gated mutations of repository tags and manage the end-to-end GitHub release publishing process.

What is the best way to enforce disciplined versioning and release notes for research projects?▼

The best way to enforce disciplined versioning is to automate the release ceremony using project-shape awareness. This detects research or documentation repositories and adjusts the release framing to generate appropriate semver tags and release notes.

Why does manual release orchestration fail to maintain semver compliance across software products?▼

Manual release orchestration fails due to friction and inconsistency in version bumping and tagging. Automating the end-to-end release lifecycle standardizes changelog generation and GitHub publishing to guarantee strict semver compliance.