release-clisbotlisted

# Release Clisbot Use this skill from the current `clisbot` checkout. Do not assume or record a machine-specific absolute path; verify the repo root by finding `package.json` with package name `clisbot` and the repo `AGENTS.md`. ## Hard Rules - Run `npm login` and `npm publish --access public` in an attached session. - If npm returns a browser approval URL, send that exact URL to the operator and continue the same attached session after approval. - Never use `npm publish --otp`, `npm login --otp`, or any OTP fallback. - If npm returns `EOTP` or demands OTP instead of browser approval, stop and ask; do not invent a manual OTP path. - Do not publish until version, docs, release notes, migration decision, gates, and package dry-run are aligned. - If any release path, version, tag, or migration requirement is unclear, ask before publishing. - Do not include local machine paths in release notes, GitHub Releases, or skill reports unless the operator explicitly asks for a local filesystem path. ## Preflight 1. Start from the current checkout root, not a hard-coded path: ```bash test "$(node -p "require('./package.json').name")" = "clisbot" ``` 2. Read `AGENTS.md` and `docs/development/README.md`. 3. Inspect `git status --short`, `package.json`, `CHANGELOG.md`, `docs/releases/README.md`, `docs/releases/upcoming.md`, `docs/migrations/index.md`, and the latest `docs/updates/releases/*-release-guide.md`. 4. Decide the release lane: first beta, next beta, or official stab