bump-release

Automate software releases by updating CHANGELOG, package.json, and Git tags.

69|3|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/PaulRBerg/agent-skills --skill bump-release-paulrberg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-release
Source: https://github.com/PaulRBerg/agent-skills/tree/main/skills/bump-release
Command: npx skills add https://github.com/PaulRBerg/agent-skills --skill bump-release-paulrberg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the release process by updating the CHANGELOG, bumping the version in package.json, and creating Git tags, reducing manual release toil.

Core Features & Use Cases

  • Automatic changelog updates for regular releases and beta workflows.
  • Version bumps in package.json with optional explicit version or automatic inference.
  • Git commits and tagging with conventional messages; supports dry-run previews to verify changes.

Quick Start

Run a standard release with /bump-release. To set a specific version, use /bump-release 2.0.0. For a beta release, use /bump-release --beta. To preview changes without applying them, use /bump-release --dry-run.

Frequently Asked Questions about bump-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate my npm package releases with changelog and version bumps?

Automate releases by running a single command that updates your CHANGELOG, bumps the version in package.json, and creates Git tags with conventional commit messages. The Skill handles version inference automatically or accepts an explicit version number you provide.

Can I preview release changes before they're committed?

Yes, use the dry-run option to preview all changes—changelog updates, version bumps, and Git tags—without applying them. This lets you verify the release output before committing.

How do I run a beta release with version tags?

Use the beta flag to automate beta releases with appropriate versioning and tagging. The Skill manages beta version formatting and Git tags while following the same changelog and commit conventions as regular releases.

What happens to my code formatting during an automated release?

If a justfile exists in your project, the Skill automatically formats affected files during the release process. This ensures your CHANGELOG and package.json stay consistent with your project's formatting standards.

Does the release process work without manually specifying a version?

Yes, the Skill derives the next version automatically based on your existing version and commit history. You can also set an explicit version when needed, giving you flexibility between automatic and manual versioning.