release
Skill0 starsChanged 8 months agoMITView on GitHub
Bump the .claude-plugin version (patch, minor, or major) in plugin.json and marketplace.json, commit, and push. Use when the user wants to release a new version, or invokes /release.
- Commits and pushes
196 other projects use a version of this.
Adopted by
Most recently taken up by
- zxcvbn-ts/zxcvbntheir own version, first seen Nov 9, 2026
- TechbeeAT/jtxBoardtheir own version, first seen Nov 9, 2026
- ddnexus/pagytheir own version, first seen Nov 9, 2026
- zerx-lab/FluxDowntheir own version, first seen Nov 9, 2026
- orioledb/orioledbtheir own version, first seen Nov 9, 2026
- AmruthPillai/Reactive-Resumetheir own version, first seen Nov 8, 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
- GrinvSkill
docs-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 AzureSkill
documentation-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 versions196 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 196
- paperclipai/paperclip★ 112ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 72ksame name
- traefik/traefik★ 65ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 63ksame name
- AmruthPillai/Reactive-Resume★ 45ksame name
- amruthpillai/reactive-resume★ 45ksame name
- reactive-resume/reactive-resume★ 45ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
186 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 repository8 other files it gives its agents.
- fix-englishSkill
- mac-llm-fitSkill
- pushSkill
- repo-metaSkill
- research-apisSkill
- run-appSkill
- write-user-guideSkill
- write-user-storySkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 186 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Check if the user specified a bump type in their message:
- Distinctive: line 21
If not specified, default to patch.
- Very specific: line 25
Read .claude-plugin/plugin.json and extract the current version field.
- Very specific: line 33
Update the version field in:
- Very specific: line 43
Commit with message: Bump version to <new_version>
- Very specific: line 58
ALWAYS update both plugin.json and marketplace.json — they must stay in sync
- Distinctive: line 59
NEVER amend an existing commit — always create a new one
- Distinctive: line 60
If there are other uncommitted changes, commit ONLY the two version files — do not include unrelated changes
- Distinctive: line 61
If the push fails, show the error and suggest the user fix it manually (e.g., set upstream, resolve conflicts)
“Common” is measured: kept by at least 6 in 10 of the 186 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
Bump the plugin version, commit the change, and push to remote.
Process
Step 1 — Determine the bump type
Check if the user specified a bump type in their message:
patch(default) — e.g., 0.1.2 → 0.1.3minor— e.g., 0.1.2 → 0.2.0major— e.g., 0.1.2 → 1.0.0
If not specified, default to patch.
Step 2 — Read the current version
Read .claude-plugin/plugin.json and extract the current version field.
Step 3 — Calculate the new version
Increment the appropriate segment based on the bump type. Reset lower segments to 0 when bumping minor or major.
Step 4 — Update version in both files
Update the version field in:
.claude-plugin/plugin.json.claude-plugin/marketplace.json(inside theplugins[0].versionfield)
Both files must have the exact same new version.
Step 5 — Commit and push
- Stage both files:
git add .claude-plugin/plugin.json .claude-plugin/marketplace.json - Commit with message:
Bump version to <new_version> - Push to the current remote branch:
git push
Step 6 — Confirm
Output:
✅ Released v<new_version> (was v<old_version>)
Bump: <patch|minor|major>
Pushed to: <branch>Rules
- ALWAYS update both
plugin.jsonandmarketplace.json— they must stay in sync - NEVER amend an existing commit — always create a new one
- If there are other uncommitted changes, commit ONLY the two version files — do not include unrelated changes
- If the push fails, show the error and suggest the user fix it manually (e.g., set upstream, resolve conflicts)
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.