What problem does it solve?
This Skill codifies a battle-tested release process that prevents broken npm publishes caused by workspace leaks, incorrect publish commands, improper npm tokens, draft releases, or invalid version formats, and reduces long recovery windows after failed releases.
Core Features & Use Cases
- Pre-publish validation: Scan packages/*/package.json for file:/link: references, absolute paths, and non-semver versions to stop faulty publishes before they start.
- Safe publish commands: Enforce per-package cd && npm publish --access public usage instead of workspace-scoped or -w publishes that hang with 2FA.
- Fallbacks and verification: Define one-retry fallback to local publish, post-publish smoke tests, CI publish-policy gating, and guidance on automation tokens and GitHub release behavior.
- Use case: Release managers and CI pipelines for a monorepo can run these checks to ensure reliable promotion from dev→preview→main and successful npm and GitHub Release workflows.
Quick Start
Run the pre-publish validation across packages, then cd into each package directory and publish with npm publish --access public, and finally perform the post-publish smoke test to verify the release.