← ClaudeAtlas

atmos-cli-releaselisted

Run the standalone Atmos CLI release workflow for this repository. Use this whenever you need to cut an Atmos CLI release, verify `apps/cli/Cargo.toml`, create or dispatch the required `cli-v<version>` GitHub Release, and publish CLI archives. Prefer this over local runtime or generic GitHub release flows for CLI releases.
AruNi-01/atmos · ★ 2 · Web & Frontend · score 69
Install: claude install-skill AruNi-01/atmos
Atmos-specific standalone CLI release workflow. Use this skill when publishing the `atmos` CLI as an independent control-plane artifact for agents, scripts, Desktop, Web, and Local Runtime integrations. ## What this skill owns This skill handles the Atmos CLI release sequence: 1. validate repository state 2. validate the CLI version in `apps/cli/Cargo.toml` 3. optionally build the CLI locally for a spot check 4. publish a stable `cli-v<version>` release from `main`, or a prerelease test release from an explicit ref 5. rely on GitHub Actions to build and upload CLI archives 6. verify the published GitHub Release assets 7. verify `atmos update` and Settings > About can discover the stable release The repository-specific execution wrapper lives in the bundled script: - `scripts/atmos-cli-release.mjs` Use that script for operational steps. Keep this file focused on orchestration and decision-making. This skill does not own the local runtime release flow, `@atmos/local-web-runtime`, Desktop release packaging, or Homebrew tap updates. Keep those in `atmos-local-web-release` and `atmos-desktop-release`. ## Repository release model Atmos CLI releases follow these rules: - CLI tag format is `cli-v<version>` - CLI package version is sourced from: - `apps/cli/Cargo.toml` - CLI release workflow: - `.github/workflows/release-cli.yml` - stable tag push releases must point at a commit already contained in `origin/main` - prerelease test releases should use `workflow_dispatch`