release

Automate npm package releases and GitHub publishing by running a preflight workflow that bumps versions, drafts a changelog, updates metadata files, and publishes across channels. This ensures synchronized versioning and delivery without manual intervention.

Version bump propagation updates the version number across package.json, .claude-plugin/plugin.json, and SKILL.md frontmatter simultaneously. Determining the bump from package.json ensures all plugin metadata files remain synchronized during the release process.

Generate a changelog for a Claude Code marketplace release by drafting entries in Keep a Changelog format. The release workflow automatically drafts and appends these entries to CHANGELOG.md before publishing to all channels.

Yes, you need a clean working tree before starting an automated versioning workflow. Preflight checks validate the current branch and working tree status to ensure no uncommitted changes interfere with the release process.

Yes, you can create a GitHub release when publishing npm package updates. The multi-channel publishing workflow optionally creates a GitHub release alongside updating metadata files and publishing to the Claude Code marketplace and npm.

Preflight checks fail when releasing a new Coach version if the current branch is incorrect or the working tree contains uncommitted changes. These checks enforce a clean state before proceeding with version bumps and multi-channel publishing.