Release Skill

Use this skill when preparing or executing a Pake release. Shared facts live in AGENTS.md and are not repeated here: the four version files and tag format (Version Management), CI jobs, Trusted Publishing, surface separation, and the contributors bot (Release Workflow), and issue closeout (Issue Closeout After a Fix).

Pre-Release

1. Before changing files or running any formatter/build, freeze the full baseline with git status --short --branch -uall, git diff, and git diff --cached. If the checkout contains unrelated or ambiguously owned changes, prepare the release in an isolated worktree.
2. Confirm the new version (jq .version package.json; previous tag per AGENTS.md Version Management) and that npm view pake-cli@X.Y.Z version returns 404.
3. Update all four version files.
4. pnpm run format, then pnpm test. If pnpm test fails at the suite's pnpm install pake-cli@latest (run in /tmp) against a mirror, re-run once; two consecutive failures are real.
5. pnpm run cli:build, then pnpm run release:check (version sync, format, vitest, package contents, npm dry-run).
6. Re-read git status --short --branch -uall, git diff, and git diff --cached. Restore only build-churn paths that were clean in the baseline and provably generated by this run; otherwise repeat in an isolated worktree.
7. Commit chore: bump version to VX.Y.Z with the rebuilt dist/cli.js staged via git add -f dist/cli.js.

Tag And Verify