release-publish
Skill0 starsChanged 18 days agoMITView on GitHub
Cut and publish a release with version bump, changelog notes, annotated tag, CI-built artifacts, and a post-release verification check. Use when verified work is ready to ship, when asked to release, publish, deploy, or cut a version, or when closing a delivery cycle.
- Commits and pushes
9 other projects use a version of this.
Adopted by
Most recently taken up by
- skforecast/skforecasttheir own version, first seen Nov 16, 2026
- Shri-Phnx/claude-skillstheir own version, first seen Oct 13, 2026
- bkywksj/knowledge-basetheir own version, first seen Oct 8, 2026
- clawwork-ai/ClawWorktheir own version, first seen Oct 8, 2026
- mono/SkiaSharptheir own version, first seen Oct 8, 2026
- chrysb/alphaclawtheir own version, first seen Oct 8, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- mono/SkiaSharp★ 5.6ksame name
- skforecast/skforecast★ 1.5ksame name
- chrysb/alphaclaw★ 1.5ksame name
- clawwork-ai/ClawWork★ 533same name
- bkywksj/knowledge-base★ 346same name
- hhhyyyy99/prot-skills★ 7same name
- Shri-Phnx/claude-skills★ 2same name
- KcAnom/pi-fairy-tales-chains★ 0same name
- metyatech/skill-release-publish★ 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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- planner-executor-handoffSkill
- research-loopSkill
- test-gateSkill
- work-trackingSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
3
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 15
Notes: Write the changelog for the reader of the diff: what changed, why, what they must do.
- Distinctive: line 45
No release without a green test gate behind it.
- Distinctive: line 46
No release notes that only a committer could parse.
“Common” is measured: kept by at least 6 in 10 of the 8 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 publish
Goal: ship what was verified, and prove it works from the outside. Phase
doc: docs/workflows/06-publishing.md. A human co-signs this phase, always.
Checklist
- Version. Bump per the consumer repo's policy (semver default). Breaking changes are major bumps; surprises are defects.
- Notes. Write the changelog for the reader of the diff: what changed, why, what they must do. Generated notes are a draft; edit them. Reference the work-item IDs being closed.
- Tag. Annotated tag on the merge commit:
git tag -a vX.Y.Z -m "Release vX.Y.Z: closes <work-item ids>"
git push origin vX.Y.ZThe tag push is what the release workflow listens for
(docs/templates/release.yml, copied to
.github/workflows/release.yml in the consumer repo): it reruns
make test-unit, drafts notes from the Conventional Commits between the
previous tag and this one, creates the GitHub Release, and runs the
post-release check named in the POST_RELEASE_CHECK repository variable.
4. Artifacts. Everything consumers receive is built by CI and attached
to the release, never built on a laptop (the build step in the workflow
is the place).
5. Publish. Push through the consumer's channel: GitHub Release (the
workflow's gh release create), package registry, az pipelines run,
deployment. Use the same work-item ID trail so the release links back to
its evidence.
6. Verify from outside. One concrete check that the published thing
works as a consumer sees it: install it, hit the endpoint, run the smoke
test. The workflow runs POST_RELEASE_CHECK when set; record the result
on the release work item either way.
Rules
- No release without a green test gate behind it; link the evidence.
- No release notes that only a committer could parse.
- Rollback plan stated in the notes when the change touches runtime behavior.
Close the loop
Within a day, file what the cycle taught: follow-ups, debt, new research questions. That backlog is the next cycle's research input.
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.

