← ClaudeAtlas

releaselisted

Cut a release of the Claude Code Orchestrator extension — bump the version, update the changelog and release notes, build the .vsix, and publish to the VS Code Marketplace (vsce) and Open VSX (ovsx). Use when the user says "release", "cut a release", "publish the extension", "ship v1.x", "bump and publish", or asks to deploy a new version to the marketplaces.
Toragonite/claude-code-orchestrator · ★ 1 · AI & Automation · score 72
Install: claude install-skill Toragonite/claude-code-orchestrator
# Release the extension End-to-end release workflow for this VS Code extension: version bump → changelog/release notes → build → verify → publish to both marketplaces → tag. The build/publish plumbing already exists in `package.json` scripts (`package`, `publish`, `publish:ovsx`, `publish:all`); this skill sequences them safely and fills in the human steps around them. ## Inputs - **Target version** — read from the user's request (e.g. "release v1.4.0"). If they only say "release" or "bump", infer the bump from the work since the last tag: new user-facing feature → minor; fixes only → patch; breaking change → major (SemVer). State the version you picked and proceed; it is reversible before publish. - **Marketplaces** — default BOTH (VS Code Marketplace via `vsce`, Open VSX via `ovsx`). Only skip one if the user says so. ## Preconditions (check first, do not skip) 1. **Clean-ish tree / right branch.** `git status`. Release from a release branch or `main` per the repo's convention (`git branch --show-current`). Uncommitted *release* edits (version, changelog) are expected; unrelated uncommitted work is a stop-and-ask. 2. **Publisher auth exists.** Publishing needs tokens the operator holds, NOT committed: - `vsce` needs a VS Code Marketplace PAT (`VSCE_PAT` env var, or `vsce login <publisher>`). - `ovsx` needs an Open VSX token (`OVSX_PAT` env var, or `ovsx create-namespace`/`--pat`). Do not ask the user to paste tokens into the chat. If a publish st