cutting-a-release
Skill4 starsChanged 6 months agoMITView on GitHub
Cut a Superpipelines version release (vX.Y.Z) — verify the 5 version targets agree, draft CHANGELOG + RELEASE-NOTES entries, land them via PR (main is branch-protected), 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 Superpipelines.
- 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/aiboardingedited, first seen Aug 28, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- gustavo-meilus/aiboarding★ 240% 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- cutting-a-releaseSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 0 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
mainis branch-protected: No direct git push origin main. - Very specific: line 13
JSON must be BOM-free: Never Set-Content -Encoding UTF8 for JSON.
- Very specific: line 14
5 version targets must agree: before tagging: package.json, .Codex-plugin/plugin.json, .Codex-plugin/marketplace.json (plugins.0.version — …
- Very specific: line 15
Tag ↔ changelog convention: every tag vX.Y.Z MUST have a matching ## X.Y.Z CHANGELOG entry and a ## vX.Y.Z RELEASE-NOTES entry before gh …
- Very specific: line 16
gh CLI in Bash tool: never --body @'...'@ (PowerShell here-string, fails).
“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 a Superpipelines Release
Cut a version release after the feature PR(s) are merged into main. Full step detail + gotchas live in RUNBOOK.md — read it before acting.
Hard constraints (read first)
mainis branch-protected. No directgit push origin main. Every change goes through a PR.gh pr merge <n> --squash --adminbypassesREVIEW_REQUIRED(CI must still be green) — confirm with the user before any--adminoverride.- JSON must be BOM-free. Never
Set-Content -Encoding UTF8for JSON. Use the Edit tool orpython3writes (encoding="utf-8"). - 5 version targets must agree before tagging:
package.json,.Codex-plugin/plugin.json,.Codex-plugin/marketplace.json(plugins.0.version— NOT the top-level1.0.0),.cursor-plugin/plugin.json,AGENTS.md(- **Project Version**: vX.Y.Z). First 3 listed in.version-bump.json; last 2 are manual. - Tag ↔ changelog convention: every tag
vX.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.
Workflow
- Preflight —
git fetch origin; confirmorigin/mainhas the feature merge; verify all 5 version targets agree and equal the intended vX.Y.Z (npm run check:versionscovers 6 including.codex-plugin); check tag/release naming convention (vX.Y.Z — <Title Case Name>). Profile-drift check: confirm the latest "Profile drift review" issue (opened monthly by.github/workflows/profile-drift.yml) is closed or its findings are consciously deferred in the release notes; amodel_tiers_versionolder than 90 days blocks unless deferred. - Sync local main —
ExitWorktree action:keepif in a worktree;git checkout main && git pull --ff-only origin main(clear stale untracked blockers first — diff againstorigin/main). - Draft doc entries — add
## X.Y.ZtoCHANGELOG.mdand a<release_entry>toRELEASE-NOTES.md, mirroring the previous entry's format exactly. Source bullets from real changes; do not invent. - Land docs via PR — branch
release-notes-X.Y.Z, commit, push,gh pr create(--body-file), wait for CI pass, confirm intent,gh pr merge --squash --admin --delete-branch, re-sync main. - 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;Closes #Nissues CLOSED; follow-up issues still OPEN. - Aiboarding pointer (optional) — if release docs don't touch the 3 AIBOARDING sections, no-op advance
last_synced_committo HEAD via the same PR +--adminflow. Expect one residual drift nag on the bump commit — STOP, do not chase.
Gotchas checklist
- Bumped
plugins.0.versionin marketplace.json, not top-level1.0.0. - All 5 version targets agree before tagging (
npm run check:versions). - Latest profile-drift review issue closed or explicitly deferred.
- CHANGELOG + RELEASE-NOTES entries exist before
gh release create. - Used
--body-filefor all gh bodies (never@'...'@). - No direct push to main — everything via PR.
- Got user OK before any
--adminoverride. - 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.

