release
Skill2 starsChanged 4 months agoMITView on GitHub
Cut a release — pick the next version, bump it in the manifest, update the changelog, and create the tag and release notes. Use when the user says "cut a release", "prepare a release", "bump the version", "tag a release", "ship a new version", or "release X.Y.Z".
- 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
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 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
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
rivet-devSkilllaunch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
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 repository68 other files it gives its agents.
- a11ySkill
- api-docsSkill
- audit-logSkill
- benchmarkSkill
- bisectSkill
- cacheSkill
- changelogSkill
- cherry-pickSkill
- ci-setupSkill
- codeownersSkill
- commit-messageSkill
- connection-poolSkill
- contributingSkill
- coverageSkill
- db-migrateSkill
- dead-codeSkill
- debugSkill
- depsSkill
- diagramSkill
- dockerizeSkill
- docstringSkill
- e2eSkill
- env-exampleSkill
- error-handlingSkill
- explainSkill
- feature-flagSkill
- flaky-testSkill
- gitignoreSkill
- graceful-shutdownSkill
- graphqlSkill
- healthcheckSkill
- i18nSkill
- idempotencySkill
- licenseSkill
- lint-fixSkill
- loggingSkill
- migrateSkill
- mockSkill
- onboardSkill
- optimizeSkill
- paginationSkill
- pr-descriptionSkill
- pre-commitSkill
- profileSkill
- prune-branchesSkill
- rate-limitSkill
- readmeSkill
- rebaseSkill
- refactorSkill
- regexSkill
- resolve-conflictsSkill
- retrySkill
- review-diffSkill
- scaffoldSkill
- secrets-scanSkill
- security-headersSkill
- seedSkill
- soft-deleteSkill
- sqlSkill
- squashSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 37
Don't push or publish (git push, git push --tags, npm publish, gh release create) unless the user explicitly asks — stop after the local …
- Distinctive: line 38
Never invent a changelog entry that isn't backed by a commit.
- Distinctive: line 39
Keep version, tag, changelog heading, and commit message all referring to the same version string — no drift.
- Distinctive: line 40
If the bump level is ambiguous or the commits suggest a breaking change the user didn't flag, surface it and confirm before bumping.
“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
Release context
!git tag --sort=-creatordate 2>/dev/null | head -5
!ls package.json pyproject.toml Cargo.toml composer.json VERSION CHANGELOG.md 2>/dev/null
!git log --oneline --no-merges "$(git describe --tags --abbrev=0 2>/dev/null)"..HEAD 2>/dev/null | head -40 || git log --oneline --no-merges -40
Instructions
Cut a release for this project. Use the version or bump level in $ARGUMENTS; if none is given, infer the right semver bump from the commits since the last tag (breaking → major, feat → minor, fix/chore → patch).
Before changing anything
- Confirm the working tree is clean and you're on the intended branch. If there are uncommitted changes, stop and ask — a release should be cut from a known state.
- Find the current version in the manifest and the latest tag. Decide the next version (respect any pre-1.0 or pre-release conventions already in use).
- Review the commits since the last tag (above) to confirm the bump level matches what actually changed.
Steps
- Bump the version in the project's manifest (
package.json,pyproject.toml,Cargo.toml,VERSION, etc.). Use the native tool when it exists and the user is fine with it (npm version <level> --no-git-tag-version); otherwise edit the field directly. Keep lockfiles in sync. - Update the changelog. If a
CHANGELOG.mdexists, add a new section for this version dated today, grouping commits into Added / Changed / Fixed / Removed and rewriting them into user-facing language. If there's no changelog, hand off to thechangelogskill or generate the notes inline. Move any "Unreleased" entries under the new version. - Commit the bump and changelog together:
chore(release): vX.Y.Z. - Tag it: an annotated tag
vX.Y.Zwhose message is the release summary. Don't tag until the bump commit exists. - Draft release notes — a short highlights paragraph plus the changelog section — ready to paste into a GitHub/GitLab release.
Rules
- Don't push or publish (
git push,git push --tags,npm publish,gh release create) unless the user explicitly asks — stop after the local commit and tag and report what's ready. - Never invent a changelog entry that isn't backed by a commit. Match the existing changelog's format if one exists.
- Keep version, tag, changelog heading, and commit message all referring to the same version string — no drift.
- If the bump level is ambiguous or the commits suggest a breaking change the user didn't flag, surface it and confirm before bumping.
- End by summarizing: the version chosen, the files changed, the tag created, and the exact command(s) the user can run to push/publish when ready.
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.

