cluster-cli: Skill for Codex

Cluster CLI releases

Prepare a release before making any remote change. Treat tagging and pushing as explicit confirmation steps.

Preconditions

Run these checks before proposing a version or touching release files:

git status --short --branch
git branch --show-current
git fetch --tags origin
git tag --sort=-version:refname | head -n 1

Require all of the following for an actual release:

• Current branch is exactly main; refuse on every other branch.
• Working tree is clean.
• main is synchronized with origin/main; do not release an unpushed or divergent commit.
• Proposed vX.Y.Z is a valid, unused semver tag and matches version in Cargo.toml.

For a comparison or dry run, report failed preconditions but continue read-only where possible.

Preflight check

For release check, answer one question: is this repository in a releasable state right now? This command is strictly read-only. It never commits, stages, tags, pushes, fetches into a branch, or touches any GitHub resource, so it is safe to run at any time, on any branch, without confirmation.

Run only inspecting commands:

git branch --show-current
git status --short --branch
git fetch --tags origin
git rev-list --left-right --count origin/main...HEAD
git tag --list "v$(grep -m1 '^version' Cargo.toml | cut -d'"' -f2)"
cargo fmt -- --check
cargo clippy -- -D warnings
cargo test --verbose

git fetch is the only remote call and it updates remote-tracking refs only; never pull, merge, or rebase from this command.

Evaluate each gate independently and keep going after a failure so the user sees the full picture:

• Branch — current branch is exactly main.
• Worktree — no staged, unstaged, or untracked changes.
• Sync — main and origin/main point at the same commit, with no ahead or behind counts.
• Version — version in Cargo.toml has no matching existing vX.Y.Z tag.
• Format — cargo fmt -- --check exits clean.
• Lint — cargo clippy -- -D warnings exits clean.
• Tests — cargo test --verbose passes.