How do I install the Release skill?

Run npx skillmds@latest add byerlikaya/release 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 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?

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 free to use?

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

Who published Release?

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

Release by byerlikaya — Agent Skill

Name: Release
Author: byerlikaya

File contents

Release & CHANGELOG

Trigger phrases: "release", "cut a release", "changelog", "version bump", "bump the version", "new version", "tag", "semver"

SemVer mapping (derive from Conventional Commits)

fix: → PATCH (x.y.Z)
feat: → MINOR (x.Y.0)
BREAKING CHANGE: / feat!: → MAJOR (X.0.0)

CHANGELOG (Keep a Changelog)

Headings: Added · Changed · Fixed · Removed · Security · Deprecated. Every version is dated; the Unreleased section can be auto-populated from commits.

Pre-release gates (all must pass)

Tests green + sonarqube-check PASSED
dependency-audit clean (0 HIGH/CRITICAL)
CHANGELOG up to date
Version number conforms to SemVer
Every distribution channel has a documented way to GET this version. Publishing and reaching users are different events. A channel whose consumers pin at install time — an editor extension, a plugin, a vendored copy — leaves them on the version they installed until they ask for a new one, so a security fix ships and does not arrive. For each channel name the upgrade command in the README, and say plainly where it is not automatic. This was a real gap: three channels documented npm i -g / brew upgrade / a refresh command while the plugin channel documented only how to install.

Tagging

git tag -a vX.Y.Z -m "vX.Y.Z"    # asks for approval (§4.4); push on explicit request (§4.5)

DoD

Correct SemVer bump; complete CHANGELOG; tag + rollback plan ready.

---name: releasedescription: Versioning and CHANGELOG: SemVer mapped from Conventional Commits, Keep a Changelog format, tagging, pre-release gates. Use when cutting a version: bumping, writing the CHANGELOG entry, or tagging.---# Release & CHANGELOGTrigger phrases: "release", "cut a release", "changelog", "version bump", "bump the version", "new version", "tag", "semver"## SemVer mapping (derive from Conventional Commits)- `fix:` → **PATCH** (x.y.Z)- `feat:` → **MINOR** (x.Y.0)- `BREAKING CHANGE:` / `feat!:` → **MAJOR** (X.0.0)## CHANGELOG (Keep a Changelog)Headings: **Added · Changed · Fixed · Removed · Security · Deprecated**.Every version is dated; the `Unreleased` section can be auto-populated from commits.## Pre-release gates (all must pass)- [ ] Tests green + `sonarqube-check` PASSED- [ ] `dependency-audit` clean (0 HIGH/CRITICAL)- [ ] CHANGELOG up to date- [ ] Version number conforms to SemVer- [ ] **Every distribution channel has a documented way to GET this version.** Publishing and reaching users are different events. A channel whose consumers pin at install time — an editor extension, a plugin, a vendored copy — leaves them on the version they installed until they ask for a new one, so a security fix ships and does not arrive. For each channel name the upgrade command in the README, and say plainly where it is not automatic. This was a real gap: three channels documented `npm i -g` / `brew upgrade` / a refresh command while the plugin channel documented only how to install.## Tagging```bashgit tag -a vX.Y.Z -m "vX.Y.Z" # asks for approval (§4.4); push on explicit request (§4.5)```## DoD- Correct SemVer bump; complete CHANGELOG; tag + rollback plan ready.

Frequently asked questions

Release