release

Name: release
Availability: InStock
Author: neolao

Automate version bumps, CHANGELOG updates, documentation regeneration, and commit/tagging with Semantic Versioning.

Updated Jul 7, 2026

Search Tags:#version control #semantic versioning #release automation #release workflow #CHANGELOG management

Ready to run

npx skills add https://github.com/neolao/claude-plugin-vibe --skill release-neolao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/neolao/claude-plugin-vibe/tree/main/skills/release
Command: npx skills add https://github.com/neolao/claude-plugin-vibe --skill release-neolao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of versioned releases, managing version bumps and CHANGELOG updates, streamlining the release process for developers.

Core Features & Use Cases

Version Management: Automatically determine and bump the version based on Semantic Versioning rules.
CHANGELOG Update: Moves entries from the [Unreleased] section to the new version section of CHANGELOG.md.
Documentation Refresh: Regenerates documentation to include the new version's features.
Commit and Tagging: Automates the commit and tagging of the release.
Use Case: When you want to create a new release for your project, simply use the /vibe:release command with the version number or a semantic versioning keyword.

Quick Start

Run the /vibe:release 1.2.0 command to create a release for version 1.2.0.

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 updates for a new release?▼

Automating semantic versioning and CHANGELOG updates involves bumping the version number and moving entries from the Unreleased section to the new version section. This Skill handles that automatically while also regenerating documentation and committing the release tag.

What is the best way to create a versioned release with documentation regeneration?▼

The best way to create a versioned release with documentation regeneration is to use an automated workflow that determines the semantic version, updates the CHANGELOG, refreshes docs, and commits the tag in one step. This Skill executes that entire process.

How does semantic version bumping work with an existing CHANGELOG.md file?▼

Semantic version bumping with an existing CHANGELOG.md works by applying versioning rules to increment the number and migrating Unreleased entries to a newly created version section. This ensures the CHANGELOG accurately reflects the new release.

Can I specify a custom version number instead of a semantic versioning keyword?▼

Yes, you can specify a custom version number instead of a semantic versioning keyword. By passing the desired version directly, the automation will apply that exact number to the version bump, CHANGELOG update, and tagging process.

Do I need to manually commit and tag my project after updating the CHANGELOG?▼

No, you do not need to manually commit and tag your project after updating the CHANGELOG. The release automation handles the commit and tagging automatically once the version bump and documentation regeneration are complete.

When should I use release automation for version control management?▼

You should use release automation for version control management when your project workflows require consistent versioning, accurate CHANGELOG updates, and synchronized documentation regeneration without manual intervention.