release-cut

Automate npm package release preparation by promoting the Unreleased section in CHANGELOG.md, bumping the version in package.json, and pushing a git tag to trigger CI workflows. This coordinates pre-flight checks, version selection, and post-push instructions in a single flow.

Pre-flight checks required before cutting a release include verifying a clean working tree, confirming the correct branch, ensuring the local repository is up-to-date with the origin, and passing type-checking. These guardrails prevent accidental or broken releases.

Yes, you can use this automated release flow to prepare a new npm package version and draft a GitHub Release. It bumps the package version, updates the changelog, and pushes a git tag to trigger the necessary CI workflows automatically.

Trigger the automated version bump and changelog update by requesting a release with phrases like "cut a release", "release vX.Y.Z", or "tag a release". The skill coordinates the entire local release preparation process from there.

Yes, the release automation enforces a clean working tree before committing and tagging. It also checks that you are on the proper branch, are up-to-date with origin, and pass type-checking to ensure safe version bumps.

A limitation of automating git tag creation and package versioning locally is that it requires strict pre-flight guardrails, including a clean working tree and up-to-date branch status, to prevent pushing broken or accidental releases to trigger CI.