release

Bumps semver versions, generates changelogs, and creates git tags for releases.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/tapway/shogun-os --skill release-tapway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/tapway/shogun-os/tree/main/skills/software-development/release
Command: npx skills add https://github.com/tapway/shogun-os --skill release-tapway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually bumping version numbers, moving changelog entries, and creating git tags is repetitive and error-prone. This Skill automates the entire release workflow in one command, ensuring VERSION files, CHANGELOG.md, and git tags stay consistent. ## Core Features & Use Cases - Semver Bumping: Reads the current version from a VERSION file and applies patch, minor, or major increments according to semantic versioning rules. - Changelog Generation: Moves entries from CHANGELOG.unreleased.md into CHANGELOG.md under a dated version header, then resets the unreleased file. - Git Tagging: Commits the version bump and creates an annotated release tag (e.g., v0.2.0) ready to push. - Use Case: After merging several features, run the release command with "minor" to go from 0.1.0 to 0.2.0, automatically producing a dated changelog section and a git tag. ## Quick Start Ask the agent to release a new minor version of the project, and it will bump the VERSION file, update the changelog, and create the git commit and tag.

Frequently Asked Questions about release

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

FAQPage Schema
How do I bump a semver version and create a git tag automatically?

Run the release command with patch, minor, or major as the argument. It reads the current version from the VERSION file, increments the appropriate segment, commits the change, and creates a git tag like v0.2.0.

How to generate a changelog from unreleased entries?

Keep pending entries in CHANGELOG.unreleased.md. On release, the script moves those entries into CHANGELOG.md under a dated version header such as ## v0.2.0 (2026-09-04), then resets the unreleased file.

What happens if the VERSION file does not exist?

The script creates a VERSION file containing 0.1.0 as the starting point before applying the requested bump. This means a first release with the minor argument produces version 0.2.0.

Can I run a release with uncommitted changes in git?

No, the guardrails require a clean working tree with no uncommitted changes before releasing. Commit or stash your work first so the release commit contains only the version bump and changelog updates.

Why does the release script reject my argument?

The script only accepts exactly patch, minor, or major as its argument and exits with an error otherwise. Check for typos or extra flags, and rerun with one of the three valid bump types.