agentleFS
jianghailong-xyjianghailong-xy/orbit/.agents/skills/release/SKILL.md

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

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.
  • MicrosoftSkill

    create-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

  • GrinvSkill

    changelog-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 AzureSkill

    component-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

  • GrinvSkill

    docs-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 AzureSkill

    documentation-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

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • +3 more from Grinv

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
  1. Very specific:

    Use one vX.Y.Z tag to ship all three clients through .github/workflows/release.yml:

    line 8
  2. Very specific:

    If the package version is not the version to release, bump it.

    line 36
  3. Distinctive:

    Verify the release commit is the committed and pushed main tip:

    line 44
  4. Very specific:

    Every pushed v* tag starts all the platform jobs.

    line 76
  5. Very specific:

    If dmg fails, Android is not attached.

    line 77
  6. Distinctive:

    If a tag was pushed incorrectly, ask for confirmation before deleting the remote/local tag or cancelling its workflow.

    line 79

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cut an Orbit client release

Use one vX.Y.Z tag to ship all three clients through .github/workflows/release.yml:

JobOutput
identityRefuses 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
dmgSigned and notarized macOS DMG, GitHub Release, and Sparkle appcast
testflightSigned iOS .ipa uploaded to TestFlight
android-buildSigned Android release APK, from the android-internal environment
android-publishThe 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 version X.Y.Z; the commit-count build number distinguishes iterations.
  • Android uses the tag without v as versionName and the same commit count as versionCode; installed Android apps update to any higher versionCode.

Workflow

  1. Resolve the version. release.sh next prints 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 next

    While the package version has no tag yet (locally or on origin), it is the candidate. Once it is tagged, next is the next beta in its series, or X.Y.(Z+1)-beta.1 after a stable X.Y.Z: a beta belongs to the version it precedes. next only prints. Pass an explicit version for anything else.

  2. If the package version is not the version to release, bump it. This is the release commit: package.json, the lockfile and release-notes/<version>.md all name the same version.

    .agents/skills/release/scripts/release.sh bump next          # or: bump 0.2.0-beta.3

    Fill in every section of the notes (docs/release-notes-template.md) and commit them. bump next while the package version is still untagged and its notes exist changes nothing.

  3. Verify the release commit is the committed and pushed main tip:

    git rev-parse --abbrev-ref HEAD
    git fetch origin
    git rev-list --count HEAD..origin/main

    Require main and a result of 0. If a fix exists only on another branch, merge it into main; never tag the feature branch.

  4. State the exact resolved tag and get explicit user confirmation before tagging. Creating and pushing the tag is an external, release-triggering action.
  5. Tag it with the version package.json already carries:

    .agents/skills/release/scripts/release.sh 0.2.0-beta.3

    The helper runs the same identity gate as CI (node scripts/release-identity.mjs check-tag vX.Y.Z): it refuses a tag that disagrees with package.json, missing or placeholder notes, tracked uncommitted changes and an already-used tag (local or remote), then creates an annotated tag and pushes it to origin.

  6. 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 testflight job means upload completed; App Store Connect may still need processing time and an export-compliance answer. A green android-publish job 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. When android-build reports 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.Z or X.Y.Z-beta.N versions, and only the one package.json carries.
  • scripts/release.sh is .claude/skills/release/release.sh, byte for byte, and this skill follows the same rules (npm run test:release-identity checks it). Change both together.
  • Every pushed v* tag starts all the platform jobs. To build one Apple platform only, dispatch release.yml on main with platform=macos or platform=ios instead of creating a tag. Android never runs from a dispatch, and android-v* tags start nothing.
  • If dmg fails, 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 the android-internal environment.
  • If a tag was pushed incorrectly, ask for confirmation before deleting the remote/local tag or cancelling its workflow; those are destructive external actions.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.