release-publish
Skill0 starsChanged 4 months agoMITView on GitHub
Phase 4 of 5 in the release chain (changelog → bump → tag → publish → verify). Pushes the commit and tag, publishes to npm, and creates the GitHub release. This is the phase that touches the outside world. Trigger when the previous phase says "run release-publish next", or standalone via "release-publish", "phase 4 of release", "publish the release".
- Commits and pushes
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Alex5350/arsenaltheir own version, first seen Nov 1, 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 versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- mono/SkiaSharp★ 5.6ksame name
- chrysb/alphaclaw★ 1.5ksame name
- clawwork-ai/ClawWork★ 533same name
- bkywksj/knowledge-base★ 340same name
- hhhyyyy99/prot-skills★ 7same name
- Shri-Phnx/claude-skills★ 2same name
- Alex5350/arsenal★ 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 repository21 other files it gives its agents.
- bughunt-diagnoseSkill
- bughunt-fixSkill
- bughunt-reproSkill
- bughunt-verifySkill
- feature-ship-buildSkill
- feature-ship-reviewSkill
- feature-ship-shipSkill
- feature-ship-specSkill
- migrate-inventorySkill
- migrate-transformSkill
- migrate-verifySkill
- onboard-deepenSkill
- onboard-digestSkill
- onboard-mapSkill
- release-bumpSkill
- release-changelogSkill
- release-tagSkill
- release-verifySkill
- research-artifactSkill
- research-gatherSkill
- research-synthesizeSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 3 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
All chain state is managed by the chain tool: authoritative JSON at .pi/fairy-tales/chains/release/state.json with a human-readable …
- Very specific: line 30
Call the chain tool with action: "status", chain: "release" (a legacy .release-state.md from an older version is imported automatically):
- Very specific: line 33
If there is no run → abort: "No release run found.
- Very specific: line 34
If the run is not active with currentPhase: "publish" → abort: "Expected the run to be at phase publish but it is at <currentPhase/status>.
- Very specific: line 37
If data.package / data.version / data.changelogEntry, or the tag phase's artifacts.tag (or its summary), is missing → abort: "Phase pointer …
- Very specific: line 41
If the tool reports the chain is locked by another session, abort.
- Very specific: line 48
If this is an npm package, run npm publish --dry-run and show the file manifest.
- Distinctive: line 69
Call the chain tool:
- Distinctive: line 87
After completing this phase, output exactly:
- Distinctive: line 92
Do not start the next phase.
“Common” is measured: kept by at least 6 in 10 of the 7 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
Chain version: 2 (durable state contract — see docs/STATE-CONTRACT.md)
Phase 4 of 5: release-changelog → release-bump → release-tag → release-publish → release-verify
Overview
The outward-facing phase: push branch + tag, npm publish, and cut the GitHub release
from the changelog. Everything before this was local and reversible; publishing is
permanent, so this phase confirms the manifest before it ships.
All chain state is managed by the chain tool: authoritative JSON at
.pi/fairy-tales/chains/release/state.json with a human-readable state.md
projection beside it. Never create or edit state files by hand, and never create lock
files — the tool locks for you.
Load State
Call the chain tool with action: "status", chain: "release" (a legacy
.release-state.md from an older version is imported automatically):
- If there is no run → abort: "No release run found. Run
release-changelogfirst." - If the run is not
activewithcurrentPhase: "publish"→ abort: "Expected the run to be at phasepublishbut it is at<currentPhase/status>. Run that phase's skill instead." - If
data.package/data.version/data.changelogEntry, or the tag phase'sartifacts.tag(or its summary), is missing → abort: "Phase pointer looks right but the Phase 3 output is missing. Treat as corrupted — restart the chain or repair via chain action 'update'." - If the tool reports the chain is locked by another session, abort; a dead session's
lock can be cleared with
action: "unlock". Never create lock files yourself.
Workflow
Step 1 — Confirm what ships
If this is an npm package, run npm publish --dry-run and show the file manifest. Confirm
no secrets or stray files are in the tarball (a files allowlist should already be set).
Publishing is irreversible — do not proceed past a manifest that looks wrong.
Step 2 — Push
git push origin <branch> and git push origin v<version> (push the tag explicitly).
Step 3 — Publish to npm
npm publish. If the account requires an OTP, the user provides it (npm publish
--otp=<code>) or has an automation token configured. Treat an E403 "cannot publish over
previously published versions" as already published — verify and move on, don't retry.
Step 4 — GitHub release
gh release create v<version> --title "<package> v<version>" --notes "<changelog entry>"
using data.changelogEntry.
Step 5 — Complete the phase
Call the chain tool:
action: "complete-phase", chain: "release", phase: "publish",
summary: "pushed branch+tag; npm publish done; GitHub release created",
data: {},
artifacts: {
"npmUrl": "<npm package page URL>",
"releaseUrl": "<GitHub release URL>",
"tag": "v<version>"
}The tool validates this is the current phase, advances the run to verify, and
rewrites the JSON + markdown projection atomically.
Handoff
After completing this phase, output exactly:
Phase 4 complete. Chain state updated (
.pi/fairy-tales/chains/release/state.json). Run/release-verifyto begin Phase 5.
Do not start the next phase. Do not offer to continue. Output only the handoff line and stop.
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.

