What problem does it solve? Publishing npm packages is irreversible — versions are permanent and a bad publish cannot be undone. This Skill prevents the classic release disasters: shipping stale build output, publishing workspace-pinned dependencies that break consumers, promoting to latest without verification, and stranding a half-finished release. ## Core Features & Use Cases - Preflight gating: Verifies the release runs on merged, reviewed main with CI green on the exact release SHA, the target version is unpublished, and publish credentials actually work before any version bump. - RC-first publish flow: Bumps the lockstep package set to a release candidate, regenerates the bun lockfile, verifies packed tarballs pin siblings correctly, publishes to the next tag, and smoke-tests with both npm and pnpm in clean external directories. - Human-gated promotion: Stops for explicit confirmation before the irreversible promote-to-latest step, then handles tagging, changelog, RC deprecation, and version propagation across docs and websites. - Use Case: After merging a feature PR to main, ask the agent to "do a release of 0.11.6" and it walks every phase — preflight evidence, clean rebuild, RC publish, external smoke test, confirmation pause, promotion, and post-release verification. ## Quick Start Ask the agent to cut and publish release 0.11.6 of the @metaobjectsdev npm packages from merged main.
