cutting-a-release
Skill2 starsChanged 3 months agoMITView on GitHub
Cut an aiboarding version release (vX.Y.Z) - verify the single version target agrees, draft matching CHANGELOG + RELEASE-NOTES entries, commit to main, then create the GitHub release + tag and verify. Use when the user asks to cut/ship/publish a release, tag a version, do release work, or write release notes for aiboarding.
- Commits and pushes
4 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- HermannBjorgvin/Clawdmetertheir own version, first seen Oct 25, 2026
- johan-lindahl/session-explorertheir own version, first seen Oct 11, 2026
- TriliumNext/Triliumtheir own version, first seen Oct 8, 2026
- gustavo-meilus/superpipelinesedited, first seen May 26, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- gustavo-meilus/superpipelines★ 435% same
Wrote their own version · 3
- TriliumNext/Trilium★ 39ksame name
- HermannBjorgvin/Clawdmeter★ 2.4ksame name
- johan-lindahl/session-explorer★ 0same name
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 repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cutting-a-releaseSkill
- more-with-lessSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
- openspec-verify-changeSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
- openspec-verify-changeSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 0 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
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 13
No CI: No GitHub Actions gate - verification is rg/Read assertions + python3 -c "import json.
- Very specific: line 14
One version target: Only .claude-plugin/plugin.json (version) carries the version.
- Very specific: line 15
JSON must be BOM-free: Never Set-Content -Encoding UTF8 for JSON.
- Very specific: line 17
gh CLI in Bash tool: never --body @'...'@ (PowerShell here-string, fails).
- Very specific: line 24
Bump version if needed: - if the feature work did not already bump plugin.json, do it now (Edit tool, BOM-free).
- Very specific: line 25
Draft doc entries: - add ## X.Y.Z to CHANGELOG.md (with trailing --- separator) and a <release_entry> to RELEASE-NOTES.md, mirroring the …
“Common” is measured: kept by at least 6 in 10 of the 3 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
Cutting an aiboarding Release
Cut a version release after the feature work is merged into main. Full step detail + gotchas live in RUNBOOK.md - read it before acting.
Hard constraints (read first)
mainis NOT branch-protected. Directgit push origin mainworks; no PR or--admindance required. (Confirm with the user if they prefer a PR anyway.)- No CI. No GitHub Actions gate - verification is
rg/Read assertions +python3 -c "import json; json.load(...)". Nothing waits on green checks. - One version target. Only
.claude-plugin/plugin.json(version) carries the version.marketplace.jsonhas NO per-plugin version field - do not add one. There is no package.json /.version-bump.json/.cursor-plugin/ CLAUDE.md version. - JSON must be BOM-free. Never
Set-Content -Encoding UTF8for JSON. Use the Edit tool orpython3writes (encoding="utf-8"). - Tag ↔ changelog convention (stated in
CHANGELOG.mdheader): every tagvX.Y.ZMUST have a matching## X.Y.ZCHANGELOG entry and a## vX.Y.ZRELEASE-NOTES entry beforegh release create. - gh CLI in Bash tool: never
--body @'...'@(PowerShell here-string, fails). Write the body to a temp.md, use--body-file, thenrmit. Keep temp files out of commits. - Title form:
vX.Y.Z - <Title Case Feature Name>(matches existing releases).
Workflow
- Preflight -
git fetch origin; confirmorigin/mainhas the feature merge; verifyplugin.jsonversionequals the intended vX.Y.Z; check tag/release naming convention. - Sync local main -
git checkout main && git pull --ff-only origin main. - Bump version if needed - if the feature work did not already bump
plugin.json, do it now (Edit tool, BOM-free). - Draft doc entries - add
## X.Y.ZtoCHANGELOG.md(with trailing---separator) and a<release_entry>toRELEASE-NOTES.md, mirroring the previous entry's format exactly; extend the<overview>milestone sentence and the Roadmap. Source bullets from real changes; do not invent. - Commit to main -
git addthe changed files, commit,git push origin main. (No PR needed - main is open.) - Create release + tag - extract the new CHANGELOG section as the release body, append the install line,
gh release create vX.Y.Z --target main --title "vX.Y.Z - <Title>" --notes-file <tmp>. - Verify - tag commit ==
origin/main; release not draft/prerelease; it shows asLatest.
Gotchas checklist
- Bumped
plugin.jsonversiononly - did NOT add a version field to marketplace.json. plugin.jsonversion == intended vX.Y.Z before tagging.- CHANGELOG (
## X.Y.Z+---) and RELEASE-NOTES (<release_entry>+ overview + roadmap) entries exist beforegh release create. - Used
--body-filefor all gh bodies (never@'...'@). - JSON edits BOM-free.
- Temp files cleaned up, kept out of commits.
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.

