Skip to content
TrustedSkillsbeta
Back to all skills

Bump Release

Listed
paulrberg·vlatest·devops·MIT

This "Bump Release" skill automatically increments release numbers in your codebase, streamlining deployments and ensuring accurate version tracking.

Repository

Install on your platform

This skill no longer installs under the name bump-release. paulrberg/agent-skills has no skill named "bump-release" any more. It was renamed, moved or deleted upstream.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

paulrberg

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

Nobody has reviewed this code. TrustedSkills indexes and links skills; it does not audit, run or scan them. A skill runs with whatever access you give your agent — read the source before you install it.

Automated safety checks

scanned

We could not read this skill's source, so none of the checks below were run.

Not scanned. none of the 46 skills in the repository match this slug — it was most likely renamed or removed upstream after the registry indexed it Source recorded as paulrberg/agent-skills.
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

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.