What problem does it solve? Publishing the weegloo npm package from installer-cli/ involves many error-prone steps — npm authentication, branch and dirty-tree checks, version comparison against the registry, tests, and the publish itself. This Skill delegates all deterministic work to a release script and guides the AI through the single human decision (which version bump) plus the post-publish version-bump commit. ## Core Features & Use Cases - Scripted preflight checks: Runs release.mjs preflight to verify NPM_TOKEN auth, branch state, and published-vs-current version, returning a BLOCKED, NEEDS_BUMP, or READY verdict. - Guided release decision: When versions match, asks the user to pick patch, minor, major, or a custom version — that choice doubles as publish approval; when already ahead, it publishes directly. - Safe token handling: Writes NPM_TOKEN only to a gitignored .env file, never echoes or commits secrets, and re-verifies with npm whoami. - Post-publish commit: Commits the package.json version bump (without pushing) so the repo never falls behind the npm registry. - Use Case: A maintainer says "버전 올리고 배포" — the Skill runs preflight, asks which bump, publishes to npm with the correct dist-tag, and commits the new version. ## Quick Start Ask the AI to publish a new release of the weegloo npm package from installer-cli and let it run the preflight, handle the version bump decision, publish, and commit the bump.
