What problem does it solve? Publishing an npm package is irreversible — a version number can never be reused, even after unpublishing — and this repo's release involves three version files that must agree, a dry-run consumer smoke test, OIDC trusted publishing, and tagging the exact published commit. This Skill walks through that entire procedure with the guardrails that prevent the known failure modes. ## Core Features & Use Cases - Version bump orchestration: Updates the authoritative PACKAGE_VERSION in scripts/package-manifest.mjs, the root package.json mirror, and the lockfile, then regenerates version-stamped derived files so CI's drift guard passes. - Dry-run validation: Runs the Release workflow in dry-run mode to build the tarball and install it into a scratch Vite + React app, proving a real consumer can build it before anything ships. - Provenance-signed publish and tagging: Publishes via npm publish --provenance with OIDC trusted publishing, verifies registry propagation without re-running on a 404, and tags the exact published commit with a GitHub Release. - Use Case: After merging a new component, ask to cut a minor release — the Skill checks what shipped since the last tag, bumps all three version locations, dry-runs the workflow, publishes, and tags the published commit. ## Quick Start Ask the assistant to cut a release of the design system, for example by saying "cut a patch release of @robr0/design-system and publish it to npm".