pr-version-bump

Analyze git changes since main to determine a semantic version bump.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/hiivmind/hiivmind-blueprint-lib --skill pr-version-bump
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-version-bump
Source: https://github.com/hiivmind/hiivmind-blueprint-lib/tree/main/skills/pr-version-bump
Command: npx skills add https://github.com/hiivmind/hiivmind-blueprint-lib --skill pr-version-bump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates semantic version bump decisions and changelog preparation for software releases by analyzing PRs and commits.

Core Features & Use Cases

  • Automated version bump recommendation: Analyze commits since main and determine the appropriate MAJOR, MINOR, or PATCH increment.
  • Changelog drafting: Generate a release note entry aligned with Keep a Changelog style and keep history in sync.
  • PR prep automation: Update version files, commit changes, push the feature branch, and prepare a PR scaffold for release.
  • Use Case: On a feature branch with multiple commits, automatically choose the bump level and create a PR ready for review.

Quick Start

On a feature branch with changes since main, run the skill in Prepare mode to compute the bump, apply changes to version files, draft a changelog entry, and prepare the PR workflow. Review the generated commit messages and push the branch, then open the PR.

Frequently Asked Questions about pr-version-bump

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

FAQPage Schema
How do I automate semantic version bumps from git commits?

Automate semantic version bumps by analyzing git changes since main to determine MAJOR, MINOR, or PATCH increments based on conventional commit signals. This Skill computes the appropriate bump level and applies it directly to your version files.

How do I generate a changelog entry for a release PR?

Generate a changelog entry for a release PR by drafting release notes aligned with the Keep a Changelog style. The Skill analyzes commits since main and keeps changelog formats in sync with the version bump decision.

How does conventional commit analysis determine semver increments?

Conventional commit analysis determines semver increments by parsing commit messages since main to identify breaking changes, new features, or patches. It then maps these signals to the appropriate MAJOR, MINOR, or PATCH version bump.

Can I prepare a release branch and PR scaffold automatically?

You can prepare a release branch and PR scaffold automatically by running the Skill in Prepare mode. It updates version files, commits changes, pushes the feature branch, and generates a PR scaffold ready for review.

Does this version bump tool work with existing git release workflows?

The version bump tool works with existing git release workflows by analyzing changes on a feature branch since main. It integrates into your process by applying version updates, drafting changelog entries, and preparing the branch for PR creation without external dependencies.

When should I not use automated semver bump decisions?

You should avoid automated semver bump decisions when your commit messages do not follow conventional commit standards, as the Skill relies on these signals to accurately determine MAJOR, MINOR, or PATCH increments from git changes.