What problem does it solve? Releasing npm packages from a monorepo often fails due to workspace dependency leaks, 2FA hangs, draft releases that never trigger publish workflows, and version drift between root and sub-package manifests. This Skill encodes the pre-release validation, publish, and post-publish verification procedures that prevent those failures. ## Core Features & Use Cases - Pre-Publish Validation: Scans every packages/*/package.json for file:, link:, and absolute-path dependency references before any release is tagged. - Correct Publish Procedure: Enforces publishing from inside each package directory with npm publish --access public, never via npm -w which hangs silently with 2FA. - Fallback & Recovery: Defines a one-retry-then-local-publish fallback when workflow_dispatch fails, plus a manual gh workflow run workaround for the GITHUB_TOKEN event propagation limitation. - Post-Publish Smoke Test: Verifies the published CLI with npm install -g, version check, and doctor command in a clean shell. - Use Case: Before promoting dev to main for the @bradygaster/squad-cli release, run the checklist to confirm CHANGELOG.md has a versioned section, all three package.json files share the same semver version, and no draft GitHub Releases exist. ## Quick Start Ask the agent to run the release checklist and validate the repository is ready to publish version X.Y.Z of the npm packages.
