release
Skill1 starsChanged 8 days agoMITView on GitHub
Use when you prepare a release or choose a version number. Links the versioning and safety rules. Does not publish.
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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- apply-architectureSkill
- bootstrapSkill
- clarify-intentSkill
- code-reviewSkill
- map-workSkill
- plan-workSkill
- tdd-loopSkill
- triageSkill
- write-adrSkill
- write-prSkill
- writing-checkSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 12 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 186 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use when you prepare a release or choose a version number.
- Distinctive: line 10
Read versioning/index.md and workflow/safety.md.
- Distinctive: line 14
Read the versioning page and the safety page.
- Distinctive: line 16
Check compatibility and breaking changes.
- Distinctive: line 19
Follow the release steps on the versioning page.
- Distinctive: line 20
Verify the release as the versioning page says.
- Distinctive: line 24
If you can start subagents, use them for step 3.
- Distinctive: line 34
If you cannot start subagents, do the steps one at a time in the order of this skill.
- Distinctive: line 40
No changelog entry for this release: stop at step 3.
- Distinctive: line 41
No rights to create a tag or to do another release step: stop before step 6.
- Distinctive: line 42
No OK from the owner for this release and this version: stop at step 5.
- Distinctive: line 47
Do not invent a versioning rule or a packaging step.
“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
Use when you prepare a release or choose a version number.
Read versioning/index.md and workflow/safety.md. Those pages hold the rules. This skill does not copy them.
Steps
- Read the versioning page and the safety page.
- List the changes that this release contains.
- Check compatibility and breaking changes. Check the changelog entry for this release.
- Choose the version number. Follow the versioning page.
- Apply the publish rule. Stop when the rule does not allow the release. Do not start step 6 before this check passes.
- Follow the release steps on the versioning page. That includes packaging when the page gives packaging steps. Do not invent packaging steps. Obey any limit on which repository those steps are for.
- Verify the release as the versioning page says. If a check fails, stop.
Subagents
If you can start subagents, use them for step 3. Do steps 1 and 2 yourself. Then check compatibility and the changelog at the same time, each check in its own subagent. Give each subagent a brief that is complete without your context:
- The changes from step 2, and the current version.
- The versioning page to read.
- One task: either compatibility and breaking changes, or the changelog entry.
- What to report, and a word limit, for example 300 words.
- This line: "Report to me only. Do not publish, tag, post, approve or merge."
Then do steps 4 to 7 yourself. A report from a subagent is a claim. Check each claim that the version depends on at its source.
If you cannot start subagents, do the steps one at a time in the order of this skill.
When a piece is missing
The steps expect a changelog entry, the rights to create a tag and the owner's OK for this release. If a piece is missing, stop and report it. Do not guess the missing piece.
- No changelog entry for this release: stop at step 3. Report that the entry is missing. Do not write an entry that nobody reviewed.
- No rights to create a tag or to do another release step: stop before step 6. Report the step and the right that is missing. Do not use other rights and do not change the protection.
- No OK from the owner for this release and this version: stop at step 5. Report the version that you chose and ask the owner. An OK for a different version is not the OK.
Rules
- An agent publishes or releases only with the owner's explicit OK for that release. The OK names the exact version. It never covers a production deploy or a project's release workflow.
- Do not invent a versioning rule or a packaging step.
- One agent can do all the steps. Many agents can share the steps. A skill does not make one role into one agent.
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.