How do I install the Release Version skill?

Run npx skillmds@latest add fedoroff-vlad/release-version in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Release Version safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release Version?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release Version free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release Version?

fedoroff-vlad (@fedoroff-vlad) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release Version by fedoroff-vlad — Agent Skill

Name: Release Version
Author: fedoroff-vlad

Release Version

Use when cutting a stable/production release of THIS project. Fires on: "cut a release", "bump the version", "tag a release", "ship to prod", "release notes". Determines the semver bump from merged PRs, updates version files, generates a changelog, and tags. Distinct from bump-deps (incoming deps vs outgoing version).

fedoroff-vlad Updated Sep 21, 2026

File contents

release-version — cut a stable outgoing version

This is about the project's OWN version, not its dependencies. Reproducible and deliberate — production cadence, not a routine merge.

Procedure

Find the last release: the latest tag / version file value.
Gather the delta: list merged PRs / commits since that tag.
Decide the bump (semver): breaking change → major, new feature → minor, fix only → patch. State the reasoning from the delta; ask the user if the delta is ambiguous rather than guessing major/minor.
Update version files: bump every place the version is declared (manifest, about screen, __version__, etc.). Consult .skills/change-map.yaml for a "project version" coupling if present.
Changelog: generate a human-readable changelog section from the delta, grouped (Added / Changed / Fixed). Link PRs.
Green gate: confirm the default branch is green before tagging — never tag a red build.
Tag: create the annotated tag. Pushing the tag / triggering the prod deploy is outward-facing — confirm with the user before pushing.

Output

The chosen version + why, the changelog section, files bumped, and the tag command (executed only after the user confirms the push). Stop before any irreversible publish step and ask.

Frequently asked questions