release-publish
Skill533 starsChanged 5 months agoApache-2.0View on GitHub
Prepare and publish a ClawWork desktop release or prerelease. Use when: user says "release", "publish beta", "发版", "发布 beta", "发 beta", "cut a release", or asks to ship a version tag.
- 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
- mono/SkiaSharptheir own version, first seen Oct 8, 2026
- chrysb/alphaclawtheir own version, first seen Oct 8, 2026
- metyatech/skill-release-publishtheir own version, first seen Jul 22, 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
- bkywksj/knowledge-base★ 340same name
- hhhyyyy99/prot-skills★ 7same name
- Shri-Phnx/claude-skills★ 2same name
- Alex5350/arsenal★ 0same 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
- pr-cleaner-masterSkill
- pr-merge-runnerSkill
- sync-gateway-docsSkill
- team-createSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Do not open a PR unless the user explicitly asks for one.
- Distinctive: line 19
Commit release prep with git commit -s.
- Distinctive: line 20
Do not push commits or tags without explicit user approval.
- Very specific: line 25
Read AGENTS.md, docs/agent-rules/git-conventions.md, and the release section in DEVELOPMENT.md.
- Very specific: line 43
Update packages/desktop/package.json to the release version.
- Distinctive: line 61
Only after the user explicitly approves pushing:
- Distinctive: line 63
Create the tag on the release prep commit:
- Very specific: line 94
If the release body is empty, confirm publish-release-notes filled it.
“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
Project-specific workflow for publishing ClawWork desktop releases.
Rules
- Release from
mainonly. - Do not open a PR unless the user explicitly asks for one.
- For prereleases, use tags like
v0.0.15-beta.4. packages/desktop/package.jsonversion must exactly match the tag withoutv.- Commit release prep with
git commit -s. - Do not push commits or tags without explicit user approval.
- The canonical local verification gate is
pnpm check.
Preflight
- Read
AGENTS.md,docs/agent-rules/git-conventions.md, and the release section inDEVELOPMENT.md. - Check repo state:
git status --short --branch git fetch --tags origin git tag --sort=-creatordate | head -20 git log --oneline --decorate -20 - Confirm
mainis clean and synced withorigin/main. - Identify the next version from the latest tag and user intent.
- Review unreleased commits:
git log --format='%h %s' <previous-tag>..HEAD node scripts/generate-release-notes.mjs <previous-tag>..HEAD
Prepare Commit
- Update
packages/desktop/package.jsonto the release version. - Run:
pnpm check - Inspect the final diff:
git diff -- packages/desktop/package.json git status --short - Stage only intended files.
- Commit:
git commit -s -m "chore(release): prepare vX.Y.Z[-beta.N]"
Publish
Only after the user explicitly approves pushing:
- Create the tag on the release prep commit:
git tag vX.Y.Z[-beta.N] - Push the commit and tag:
git push origin main git push origin vX.Y.Z[-beta.N] - Monitor the workflow:
gh run list --workflow release.yml --limit 5 gh run watch <run-id>
Post-Publish Verification
- Confirm
release.ymlsucceeded. - Confirm GitHub Release exists and is not draft:
gh release view vX.Y.Z[-beta.N] --repo clawwork-ai/clawwork --json tagName,isDraft,isPrerelease,isLatest,assets - Confirm expected assets are present:
- macOS arm64 DMG + zip + blockmaps
- macOS x64 DMG + zip + blockmaps
- Windows x64 NSIS installer + blockmap
- Linux x64 AppImage and deb
latest-mac-arm64.ymllatest-mac.ymllatest.ymllatest-linux.yml
- If the release body is empty, confirm
publish-release-notesfilled it.
Failure Handling
- Version mismatch: update
packages/desktop/package.json, recommit, move or recreate the tag only after confirming with the user. - Missing assets: inspect the failed matrix job first; do not re-run blindly.
- macOS notarization failure:
release.ymlhas an ad-hoc fallback. Treat non-notarization macOS failures as real blockers. - Failed local
pnpm check: fix root cause before publishing.
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.

