release
/release
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.
- Author
- byerlikaya ↗
- Repository
- claude-starter-kit ↗
- Licence
- MIT
- Last repository change
- 22.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 1
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
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.
Original author description
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.
How it works
- SemVer mapping (derive from Conventional Commits)
- CHANGELOG (Keep a Changelog)
- Pre-release gates (all must pass)
- Tagging
- DoD
SKILL.md preview
---
name: release
description: |
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 & CHANGELOG
<!-- routing-eval reads the next line; why it sits in the body: AGENT_TEMPLATE.md -->
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
- [ ] **The release commit is a diff too (§4.6).** A `chore(release)` bump, a CHANGELOG-only edit and a docs-site
version touch each stage a diff, and §4.6 exempts nothing by size — `crew-review-agent` runs over them like
any other. A version that disagrees with the tag, a CHANGELOG entry naming the wrong one, a generated
manifest edited by hand: that is what this review is for, and all three have shipped before.
- [ ] **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.
## Tagging
```bash
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.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · byerlikaya/claude-starter-kit | 100 | MIT |
| josephfung/curia | 100 | MIT |
| max-sixty/worktrunk | 100 | MIT |
| gtapps/hermitd | 100 | MIT |
| gtapps/hermitd | 100 | MIT |
| anthony-chaudhary/fak | 100 | Apache-2.0 |
| tractorjuice/arc-kit | 100 | MIT |
| drvoss/everything-copilot-cli | 100 | MIT |
| sma1lboy/rove | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version d838ad4acef7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 2 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100changelog
Keep a Changelog format. Covers structure, change types, versioning. Use when creating or updating CHANGELOG.md files following the Keep a Changelog specification, or applying semver-compatible changelog conventions. Keywords: CHANGELOG.md, semver, Keep a Changelog. - 100changelog
Generates a structured changelog from git history following Keep a Changelog format and conventional commits. Use when creating a CHANGELOG.md, preparing release notes, or when the user mentions changelog or release history. - 100changelog-keeper
Maintains a human-readable CHANGELOG.md in Keep a Changelog format from git history, suggests the next Semantic Version from Conventional Commits, and drafts release notes. Use when the user asks to update the changelog, prepare a release, bump a version, or write release notes. - 100since
Use the `since` tool to manage releases, changelogs and versioning driven by git history and conventional commits. Use when asked to perform a release, cut a version, generate or update a CHANGELOG, work out the next semantic version, list changes since the last release, or… - 90changelog-generator
Generate changelogs and release notes from Conventional Commits with semver bump detection, Keep a Changelog formatting, and monorepo scopes. Use when preparing releases, enforcing commit standards, or automating release notes. - 100release-versioning
Discipline for release classification, version bumps, and changelogs, Conventional Commits classify the release range, SemVer computes the version from those commits, Keep a Changelog renders the result. Use when the user asks to cut a release, bump a version, write a changelog,…