bump-version

Bump semantic versions in package.json and create v-prefixed Git tags.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/amanmprojects/openpaw --skill bump-version-amanmprojects
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-version
Source: https://github.com/amanmprojects/openpaw/tree/main/.agents/skills/bump-version
Command: npx skills add https://github.com/amanmprojects/openpaw --skill bump-version-amanmprojects

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bump-version helps teams keep their project metadata and release history in sync by updating version fields across manifests and Git tags when a new release is prepared.

Core Features & Use Cases

  • Update package.json or manifest files with a new semantic version (major, minor, patch) per user instruction.
  • Create and push a Git tag that matches the new version (with a v prefix) and ensure consistency between commits, tags, and manifest versions.
  • Use in CI/CD pipelines to enforce version bumps as part of release flows.

Quick Start

Run the bump-version skill on your repository to increment the version and publish a new release.

Frequently Asked Questions about bump-version

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

FAQPage Schema
How do I bump a version in package.json and create a git tag at the same time?

Bumping a version in package.json and creating a git tag requires updating the manifest file and pushing a matching v-prefixed tag. This synchronizes project metadata and Git release history in one command.

What is the best way to automate semantic versioning for git releases?

Automating semantic versioning for git releases involves incrementing major, minor, or patch numbers in manifests and tagging commits. A dedicated bump tool ensures version consistency across package files and Git tags.

Can I use a version bump tool to enforce release workflows in CI/CD pipelines?

Yes, a version bump tool can enforce release workflows in CI/CD pipelines by automatically updating package manifests and pushing v-prefixed git tags, ensuring consistent releases across automated environments.

Does bumping a project version update both the manifest and Git history?

Bumping a project version updates both the manifest and Git history by modifying version fields in package.json and creating a corresponding v-prefixed Git tag. This maintains consistency across commits and project metadata.

How do I increment patch, minor, or major version numbers for a software release?

To increment patch, minor, or major version numbers for a release, you modify the semantic version in package.json and create a matching Git tag. This accurately reflects the scope of changes in your release history.