registry-publish
Installation
SKILL.md
REGISTRY-PUBLISH — ship the package, and prove the shipped one works
Publishing is the one step in the lifecycle that cannot be undone cleanly. You cannot reliably unpublish: npm allows unpublishing only within 72 hours and only under restrictions, and a version number, once published, can never be reused. So all the safety lives before the publish, not after it. Release tooling does not do this step for you: release-please writes release notes and tags, it does not publish to a registry. This skill is the missing step.
Rules
- No publish without the user's explicit written confirmation. A version bump is not a confirmation.
- Never publish from a dirty tree. Commit first, then publish from the commit.
- Never publish a version that already exists on the registry. Check first.
- The pack list is the contract: read it before publishing, not after. If it contains a test, a secret, or source that should not ship, stop.
- Verify the published artifact after publishing: install it in a clean directory and run it. A publish that nobody verified is a rumour.
- A check that did not run is never reported as passed.