release
Skill7 starsChanged 2 days agoMITView on GitHub
Cut an Orbit client release by creating and pushing one vX.Y.Z git tag, triggering the signed/notarized macOS DMG release, the iOS TestFlight build and the signed Android APK on the same GitHub Release. Use when asked to cut or ship a release, tag a version, publish a beta, TestFlight or Android build, or start the client release workflow. Do not use for ordinary deployments of the Docker Compose stack; use the upgrade skill instead.
193 other projects use a version of this.
Adopted by
Most recently taken up by
- naomiaro/waveform-playlisttheir own version, first seen Nov 16, 2026
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- vulnerability-lookup/vulnerability-lookuptheir own version, first seen Nov 16, 2026
- ClickHouse/mcp-clickhousetheir own version, first seen Nov 16, 2026
- bpatrik/pigallery2their own version, first seen Nov 16, 2026
- Shasnow/StarRailAssistanttheir own version, first seen Nov 16, 2026
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- AmruthPillai/Reactive-Resume★ 46ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 more not listed
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.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use one vX.Y.Z tag to ship all three clients through .github/workflows/release.yml:
- Very specific: line 36
If the package version is not the version to release, bump it.
- Distinctive: line 44
Verify the release commit is the committed and pushed main tip:
- Very specific: line 76
Every pushed v* tag starts all the platform jobs.
- Very specific: line 77
If dmg fails, Android is not attached.
- Distinctive: line 79
If a tag was pushed incorrectly, ask for confirmation before deleting the remote/local tag or cancelling its workflow.
“Common” is measured: kept by at least 6 in 10 of the 183 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
Cut an Orbit client release
Use one vX.Y.Z tag to ship all three clients through .github/workflows/release.yml:
| Job | Output |
identity | Refuses the tag unless it is v + the root package.json version and carries a filled-in release-notes/<version>.md; every build job waits for it |
dmg | Signed and notarized macOS DMG, GitHub Release, and Sparkle appcast |
testflight | Signed iOS .ipa uploaded to TestFlight |
android-build | Signed Android release APK, from the android-internal environment |
android-publish | The APK, its .sha256 and android-update.json attached to the same GitHub Release, after dmg and android-build succeed |
The root package.json version is the version of record, and the tag is that version with v. The GitHub Release, the DMG/.zip names, the TestFlight marketing version, the Android versionName, the runner binaries and /dl/version.json, the Sparkle appcast and android-update.json all derive from it, and release.yml refuses a tag that disagrees with the package.
Interpret tags as follows:
vX.Y.Z: macOS stable channel, an iOS TestFlight build and an Android release.vX.Y.Z-beta.N: macOS beta channel, an iOS TestFlight build and an Android release. iOS uses numeric marketing versionX.Y.Z; the commit-count build number distinguishes iterations.- Android uses the tag without
vasversionNameand the same commit count asversionCode; installed Android apps update to any higherversionCode.
Workflow
Resolve the version.
release.sh nextprints the one tag to cut next, resolved from the package version alone; old tags are never read as a sequence:.agents/skills/release/scripts/release.sh nextWhile the package version has no tag yet (locally or on
origin), it is the candidate. Once it is tagged,nextis the next beta in its series, orX.Y.(Z+1)-beta.1after a stableX.Y.Z: a beta belongs to the version it precedes.nextonly prints. Pass an explicit version for anything else.If the package version is not the version to release, bump it. This is the release commit:
package.json, the lockfile andrelease-notes/<version>.mdall name the same version..agents/skills/release/scripts/release.sh bump next # or: bump 0.2.0-beta.3Fill in every section of the notes (
docs/release-notes-template.md) and commit them.bump nextwhile the package version is still untagged and its notes exist changes nothing.Verify the release commit is the committed and pushed
maintip:git rev-parse --abbrev-ref HEAD git fetch origin git rev-list --count HEAD..origin/mainRequire
mainand a result of0. If a fix exists only on another branch, merge it intomain; never tag the feature branch.- State the exact resolved tag and get explicit user confirmation before tagging. Creating and pushing the tag is an external, release-triggering action.
Tag it with the version
package.jsonalready carries:.agents/skills/release/scripts/release.sh 0.2.0-beta.3The helper runs the same identity gate as CI (
node scripts/release-identity.mjs check-tag vX.Y.Z): it refuses a tag that disagrees withpackage.json, missing or placeholder notes, tracked uncommitted changes and an already-used tag (local or remote), then creates an annotated tag and pushes it toorigin.Watch the shared workflow and report every job result:
gh run watch "$(gh run list --workflow release.yml -L 1 --json databaseId -q '.[0].databaseId')"A green
testflightjob means upload completed; App Store Connect may still need processing time and an export-compliance answer. A greenandroid-publishjob means the Android files are on the release (gh release view vX.Y.Z --json assets -q '.assets[].name'); its step summary lists their SHA-256. Whenandroid-buildreports that the commit was already published for Android under another tag, both Android jobs end without publishing, which is expected.
Constraints
- Accept only
X.Y.ZorX.Y.Z-beta.Nversions, and only the onepackage.jsoncarries. scripts/release.shis.claude/skills/release/release.sh, byte for byte, and this skill follows the same rules (npm run test:release-identitychecks it). Change both together.- Every pushed
v*tag starts all the platform jobs. To build one Apple platform only, dispatchrelease.ymlonmainwithplatform=macosorplatform=iosinstead of creating a tag. Android never runs from a dispatch, andandroid-v*tags start nothing. - If
dmgfails, Android is not attached. After the cause is fixed, re-run the failed jobs of that run (gh run rerun <run-id> --failed); it rebuilds the DMG and then attaches the Android build already made. Ask before re-running, as it publishes. - Required signing and publishing secrets are documented in
.github/workflows/release.yml; Android signing lives only in theandroid-internalenvironment. - If a tag was pushed incorrectly, ask for confirmation before deleting the remote/local tag or cancelling its workflow; those are destructive external actions.
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.

