What problem does it solve? Releasing npm packages from a monorepo often fails due to workspace dependency leaks, 2FA publish hangs, draft releases that never trigger workflows, and version drift between root and sub-package manifests. This Skill encodes the exact validation rules, publish commands, and fallback procedures that prevent broken releases. ## Core Features & Use Cases - Pre-Release Validation: Scans package.json files for file:/link: references, verifies root and sub-package versions match, and confirms CHANGELOG.md contains the target version section. - Correct Publish Procedures: Enforces publishing from inside each package directory (never npm -w), requires Automation-type npm tokens, and forbids draft GitHub Releases. - Fallback & Verification: Provides a one-retry-then-local-publish fallback when workflows fail, a manual gh workflow run workaround for the GITHUB_TOKEN event limitation, and a post-publish smoke test with npm install -g and version checks. - Use Case: Before tagging v0.9.5 of a two-package npm monorepo, run the release checklist to catch a stale root package.json version, publish both packages, then smoke test the CLI install. ## Quick Start Ask the agent to run the release checklist and validate the repo is ready to publish version X.Y.Z of the npm packages.
