release-prep

Pre-release workflow automation coordinates version bumps in package.json and package-lock.json, drafts CHANGELOG entries, runs validation checks, and prepares git tag commands. It operates in phases to ensure release safety without automatically pushing commits or tags to the repository.

Release preparation aborts immediately if npm run check or npm run build fails during validation. This safety constraint prevents progressing with a release when checks are not passing, ensuring only validated code proceeds to the tagging stage.

Release workflows require a clean working tree and on-main branch alignment before proceeding. The process aborts if the working tree is dirty, ensuring release safety constraints are met before any version bump or CHANGELOG drafting occurs.

Pre-release automation never pushes commits or tags automatically. It prints the exact git tag command for the user to execute manually, maintaining control over the remote repository state while still orchestrating the version bump and CHANGELOG updates locally.

Drafting a CHANGELOG entry during npm package release is handled by delegating to a dedicated changelog skill within the workflow. This ensures the entry is generated consistently as part of the version bump and validation phases before the tag command is presented.

Operating in distinct phases allows the release workflow to enforce safety constraints at each step, aborting on failed checks or dirty working trees before proceeding. This phased approach prevents incomplete or invalid releases by validating each stage before presenting the final git tag command.