Bump Release

What it does

The Bump Release skill automates the process of incrementing release numbers within your codebase, following semantic versioning principles. It handles both regular and beta releases, updating package.json and generating changelog entries. The skill can also perform a dry run to preview changes without actually modifying files or creating commits/tags.

When to use it

• You need to release a new version of your package with an incremented version number.
• You want to create a beta release with the -beta.X suffix.
• You want to see what changes would be made during a release without actually committing them (dry run).
• Your project uses a justfile for formatting and you need to ensure consistency.

Key capabilities

• Supports both regular and beta releases.
• Automatic version incrementing based on semantic versioning rules.
• Generates changelog entries by examining diffs between the current branch and the previous tag.
• Dry-run mode for previewing changes.
• Handles monorepo environments, locating packages even when in subdirectories.
• Formats files using a justfile if present.

Example prompts

• "Bump the release version."
• "Create a beta release."
• "Perform a dry run of the release process."
• "Release version 2.0.0"

Tips & gotchas

• The skill requires a clean working tree; uncommitted changes will prevent the release from proceeding and may require using a commit skill first.
• If you specify a version argument, it bypasses automatic version inference.
• The changelog generation considers files specified in the package.json's "files" field, otherwise including all changes except test changes, CI/CD workflows, and development tooling.