ops-release

To automate version bumping and changelog generation for plugin releases, use this Skill to update version numbers across multiple configuration files and create a markdown changelog based on git commit history. It automatically categorizes commits by type like feat or fix.

You can update versions in package.json, .claude-plugin/plugin.json, and src/index.ts simultaneously when preparing a release. The Skill automatically bumps version numbers across these multiple configuration files during the release workflow.

The best way to generate a markdown changelog from git commit history is using this release automation Skill, which parses commit history and categorizes entries by commit type such as feat and fix. This ensures consistent, formatted changelog output for every release.

The release workflow integrates with health checks and issue triage before proceeding to git tagging. It guides you through these preparation steps to ensure a robust release process, prompting you to confirm tagging only after checks pass.

To create and record git tags for new plugin versions, run the release preparation workflow and confirm the version bump. The Skill will update versions, generate the changelog, and then prompt you to create and record the git tag.

You should not use automated release preparation when your plugin lacks a standard git commit history for changelog generation, or when your version files are not in the supported formats like package.json or plugin.json. Manual version management is better for non-standard configurations.