release
Skill2 starsChanged 2 months agoMITView on GitHub
Cuts a new version — moves the CHANGELOG's Unreleased section into a dated SemVer version, creates the commit and the tag, and optionally the GitHub release. Use this when the user asks to publish/cut a version or prepare a release (e.g. "cut version 1.2.0", "prepare the release", "publish a new version"). It does not push without confirmation.
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- naomiaro/waveform-playlisttheir own version, first seen Nov 16, 2026
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- vulnerability-lookup/vulnerability-lookuptheir own version, first seen Nov 16, 2026
- ClickHouse/mcp-clickhousetheir own version, first seen Nov 16, 2026
- bpatrik/pigallery2their own version, first seen Nov 16, 2026
- Shasnow/StarRailAssistanttheir own version, first seen Nov 16, 2026
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- AmruthPillai/Reactive-Resume★ 46ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-auditSkill
- changelogSkill
- commitSkill
- configure-repoSkill
- copywritingSkill
- design-system-auditSkill
- i18n-paritySkill
- identitySkill
- instantiateSkill
- migration-guardSkill
- new-adrSkill
- new-specSkill
- open-issueSkill
- open-prSkill
- port-changeSkill
- prototypeSkill
- seo-auditSkill
- update-templateSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 2 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Preconditions: Verify the tree is clean (git status) and that you are on the right branch per CONTRIBUTING.md: with Git Flow the release …
- Very specific: line 23
Propose the version: Read the last published version (a v* tag or the CHANGELOG) and propose the SemVer bump from the content: breaking …
- Very specific: line 30
Sync the manifest version: If the stack has a file that declares a version, bump it to X.Y.Z in the same commit — otherwise the project …
- Distinctive: line 37
If there is none (a project with no versioned manifest), say so and carry on: the CHANGELOG is the single source of the version.
- Very specific: line 39
Commit, no tag: Create the chore(release): vX.Y.Z commit (with the AI co-authorship line from docs/conventions/ai-agents.md) on a …
- Distinctive: line 44
has no tag: if you create it, the workflow considers it published, creates no GitHub release, and on top of that the tag points at the …
- Very specific: line 80
Do NOT create the tag by hand while release.yml is active (you steal its release), do NOT push or publish without explicit confirmation, do …
- Very specific: line 81
NOT push or publish without explicit confirmation, do NOT invent changelog entries that are not in Unreleased, and do NOT skip a SemVer …
“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cut a version following Keep a Changelog and Semantic Versioning (see CHANGELOG.md
and CONTRIBUTING.md).
Automation: when merging
develop→main, the.github/workflows/release.ymlworkflow detects the most recent dated version in the CHANGELOG and, if it has no tag, publishes the tag and the GitHub release on its own. This skill prepares the cut (moving Unreleased →X.Y.Zwith a date and choosing the SemVer version); the manual tag/release is only needed if the workflow is not active.
Steps
- Preconditions. Verify the tree is clean (
git status) and that you are on the right branch perCONTRIBUTING.md: with Git Flow the release goes fromdeveloptomain, except a hotfix, which is cut on thehotfix/*branch itself (see below); withoutdevelop, frommain. If there are uncommitted changes, stop and say so. - Read what is pending. Take the entries from the
## [Unreleased]section ofCHANGELOG.md. If it is empty, there is nothing to publish: say so and stop. - Propose the version. Read the last published version (a
v*tag or the CHANGELOG) and propose the SemVer bump from the content: breaking changes → major; onlyAdded/Changed→ minor; onlyFixed/Security→ patch. Let the person confirm or correct it with AskUserQuestion. - Update the CHANGELOG. Move the
Unreleasedentries into a new## [X.Y.Z] - YYYY-MM-DDsection (today's date), leaveUnreleasedwith its categories empty and update the comparison links at the bottom of the file. - Sync the manifest version. If the stack has a file that declares a version, bump
it to
X.Y.Zin the same commit — otherwise the project publishesv0.4.0with the manifest saying0.1.0. Find the one that applies and update its lockfile too if the manager regenerates it:package.json(+package-lock.json/pnpm-lock.yaml) ·*.gemspecorlib/**/version.rb·Cargo.toml(+Cargo.lock) ·pyproject.toml·composer.json·pubspec.yaml·build.gradle·VERSION.- If there is none (a project with no versioned manifest), say so and carry on: the CHANGELOG is the single source of the version.
- Commit, no tag. Create the
chore(release): vX.Y.Zcommit (with the AI co-authorship line fromdocs/conventions/ai-agents.md) on achore/cut-vX.Y.Zbranch — remembergit-guardrails.shdoes not allow committing straight ontodevelop. Do NOT create or publish the tag here.release.ymlonly publishes if the version has no tag: if you create it, the workflow considers it published, creates no GitHub release, and on top of that the tag points at the branch commit instead of the merge onmain. - Take it to production. A PR from the cut branch →
develop, and then a PRdevelop→main. On merging intomain,release.ymlcreates thevX.Y.Ztag over the merge and publishes the release with that CHANGELOG section's notes. - Only if the workflow is not active (a project with no Actions, or
release.ymldeleted): then yes, an annotated tag by hand andgh release create vX.Y.Z --title "vX.Y.Z" --notes "<CHANGELOG section>".
The cut is the last thing before merging into main
The release job in quality.yml (.github/scripts/check-release.sh) blocks PRs toward
main if the topmost CHANGELOG version is already published, if entries were left loose
in ## [Unreleased], or if that version is inherited from the template (a CHANGELOG
that was never reset leaves the origin repository's last version on top). It is the same
rule said backwards: nothing reaches production without a version. If the PR to
main fails for that, do not dodge it — cut the version.
Hotfix (a release from main)
A hotfix/* does not go through develop, but it also publishes a version (always a
patch). The order is:
- On the
hotfix/*branch (born offmain): the fix, its entry under## [Unreleased]and the cut with this skill — steps 3 to 6, with apatchbump. - PR
hotfix/*→main. Thereleasejob validates it and, on merging,release.ymlpublishes the tag and the release. - Sync to
developwith amain→developPR (required byCONTRIBUTING.md): if you skip it,develophas neither the fix nor the CHANGELOG's version section, and the next cut overwrites it.
Example: "cut the version" → proposes v1.3.0 → CHANGELOG updated + a commit on
chore/cut-v1.3.0; the tag and the release are created by release.yml on reaching
main.
Do NOT create the tag by hand while release.yml is active (you steal its release), do
NOT push or publish without explicit confirmation, do NOT invent changelog entries that
are not in Unreleased, and do NOT skip a SemVer version.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

