← ClaudeAtlas

shiplisted

Ship the current branch's work — rebase onto master, commit, push, fast-forward master, release a patch, and install the build locally. Use when the user asks to ship, release, or publish their orchestra work.
lcsmas/orchestra · ★ 0 · Code & Development · score 72
Install: claude install-skill lcsmas/orchestra
# Ship orchestra Take the work on the current orchestra worktree branch all the way out: rebase it onto master, commit, push, land it on master, cut a patch release, and swap the local launcher to the freshly built AppImage. The release script (`scripts/release.sh`) is worktree-safe — it never checks out master (master is checked out in another worktree). `--to-master` fast-forwards `origin/master` with non-checkout pushes; `--install` atomically replaces the launcher's AppImage with the local build. ## Steps 1. **Commit any pending work.** The release refuses to run on a dirty tree. ```bash git status --short ``` If there are changes, stage and commit them with a clear message (end the message with the `Co-Authored-By` trailer, per the repo convention). 2. **Rebase onto the latest master.** `--to-master` requires the branch to be a clean fast-forward ahead of `origin/master`, so rebase first. ```bash git fetch origin && git rebase origin/master ``` Resolve any conflicts before continuing. If the rebase can't complete cleanly, stop and surface it to the user rather than forcing. 3. **Verify the build before releasing.** The release script runs the real build, but only *after* the version bump — and it never runs typecheck or tests. Catch failures now, while they're free to fix: ```bash [ -d node_modules ] || pnpm install npx tsc --noEmit && pnpm test ``` If either fails, stop and report the failures instead of