Skill · Land and release
/release$release@planr-release
Pick the next version from what changed for users, and write release notes people can read. Release prepares everything locally and publishes only when you ask.
/releasein Claude Code. If /release runs another command, use /planr:release.
$releasein Codex. With the OpenPlanr plugin for Codex, use $planr:release.
@planr-releasein Cursor. Cursor applies the planr-release rule when you mention it in chat.
What it does
Choose and maintain a product's versioning scheme, classify shipped changes, and write user-facing changelogs or release notes. Use for SemVer or CalVer decisions, version bumps, release cadence, and preparing a versioned release after landing.
Release classifies every change by one question: does a user have to do, know, or expect something different now? That classification drives the version bump and the notes. A CLI or library that others install and pin follows SemVer strictly, and the scheme you agree on is saved in .release/profile.md, so later releases follow it instead of deciding again.
The notes lead with what users can now do, describe fixes by the symptom users saw, and leave internal work out. Release prepends the new section to CHANGELOG.md, bumps versions with your repository's release tool, and stops there: pushing tags, publishing packages, and deploying happen only when you ask.
When to use it
Use it to
- Choose the next SemVer or CalVer version and write user-facing release notes
- Set up or maintain a changelog, versioning scheme, and release cadence
Not for
- Check whether unmerged work is ready to land without choosing a version
- Implement product code before release preparation
Use instead: /land$land@planr-land, /ship$ship@planr-ship
Example
/release Write user-facing release notes for everything since the last tag and update the changelog.$release Write user-facing release notes for everything since the last tag and update the changelog.@planr-release Write user-facing release notes for everything since the last tag and update the changelog.What you get
CHANGELOG.md## [Unreleased]## [1.4.0] - 2026-09-08### Removed- Entry, with the migration step inline.### Added- Entry.### Changed- Entry.### Fixed- Entry.Prompts and commands
Choose the next version number
Decide major, minor, or patch from what changed for users, not from the size of the diff.
Write release notes users can read
Turn what shipped into user-facing notes and an updated changelog that does not read like a git log.