version-bump

Determine the next semantic version from unreleased changelog JSON files and update package.json.

Updated Dec 30, 2025
One-click install
npx skills add https://github.com/kshehadeh/prompt --skill version-bump-kshehadeh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-bump
Source: https://github.com/kshehadeh/prompt/tree/main/.agents/skills/version-bump
Command: npx skills add https://github.com/kshehadeh/prompt --skill version-bump-kshehadeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of updating version numbers in package.json and applying those versions to changelog entries, ensuring consistency and saving development time.

Core Features & Use Cases

  • Semantic Versioning: Automatically determines the next version based on the highest impact level (major, minor, patch) found in unreleased changelog entries.
  • Changelog Stamping: Updates all unreleased changelog entries with the newly determined version number.
  • Use Case: After merging several features and bug fixes, run this Skill to update your project's version number and ensure all corresponding changes are correctly documented in the changelog before a release.

Quick Start

Use the version-bump skill to update the project version based on the unreleased changelog entries.

Frequently Asked Questions about version-bump

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

FAQPage Schema
How do I automate package.json version bumps and changelog updates?

Automate package.json version bumps by reading unreleased changelog entries from JSON files to determine the next semantic version. The tool updates package.json and stamps all unreleased changelog entries with the newly calculated version number.

How does semantic versioning work when calculating the next release from changelogs?

Semantic versioning calculates the next release based on the highest impact level found in unreleased changelog entries. It applies major, minor, or patch version bumps according to standard SemVer rules depending on the changes detected.

What is the best way to update project version numbers based on unreleased changelog entries?

Updating project version numbers is best handled by scanning JSON changelog files for impact levels, determining the correct SemVer increment, and automatically applying the new version to both package.json and the unreleased changelog entries.

Do I need JSON changelog files to automate semantic versioning for my release management?

Yes, you need JSON changelog files stored in your changelogs directory. The automation reads these unreleased entries to determine the highest impact level and calculate the appropriate semantic version bump for your package.

Can I use this versioning automation for major, minor, and patch SemVer releases?

Yes, this versioning automation supports major, minor, and patch SemVer releases. It evaluates the impact levels in your unreleased changelog JSON files and applies the corresponding semantic versioning rules to increment the version correctly.