What problem does it solve? Publishing a coordinated set of npm packages is risky: versions can drift, partial publishes leave ambiguous registry state, and interrupted releases are hard to recover. This Skill operates the repo's transactional release command end to end so version selection, candidate freezing, publishing, and verification happen as one journaled, resumable transaction. ## Core Features & Use Cases - Guided version selection: Derives the current version from the workspace manifest and npm, summarizes the changelog's [Unreleased] section, and requires explicit user confirmation before any release. - Transactional release execution: Runs just release-plan for read-only preflight, then just release to bump versions, qualify packages, freeze candidate tarballs, checkpoint via Graphite, publish, and verify against the registry. - Refusal and recovery handling: Interprets every refusal code via references/refusals.md, distinguishing pre-checkpoint failures (resettable with just release-reset) from post-checkpoint state (resume-only), and flags STOP conditions that must be escalated. - Use Case: A maintainer wants to ship the accumulated changes in [Unreleased]. The Skill proposes the next patch version, confirms it, runs the plan and release, answers the publish confirmation, and after verification hands off the Graphite checkpoint branch for landing. ## Quick Start Ask the agent to cut a new release of the public npm packages and let it propose the next version for your confirmation.
