skills.rest
jasoncrawford
jasoncrawfordCOMMUNITY
Explore all skills by this author →
Website𝕏@jasoncrawfordGitHub

semver

Recommends patch, minor, or major version bumps after pull requests merge.

Updated Mar 10, 2026
Search Tags:#release management#versioning#pull request#semver#version bump#breaking change
One-click install
npx skills add https://github.com/jasoncrawford/brunel --skill semver-jasoncrawford
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: semver
Source: https://github.com/jasoncrawford/brunel/tree/main/.claude-plugin/skills/semver
Command: npx skills add https://github.com/jasoncrawford/brunel --skill semver-jasoncrawford

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a pull request merges, teams often struggle to decide whether the change warrants a version bump and at what level, leading to inconsistent or incorrect releases. ## Core Features & Use Cases - Change Classification: Maps change types (bug fix, new feature, breaking change, internal refactor) to patch, minor, major, or no bump. - 0.x Versioning Rules: Applies the convention that breaking changes ship in minor bumps while the package is pre-1.0, reserving major for a stability commitment. - Breaking Change Detection: Defines what counts as breaking, such as removing commands, flags, exported APIs, config keys, or dropping platform support. - Use Case: An agent merges a PR that adds a new CLI flag and removes a deprecated config key; the skill recommends a minor bump (while at 0.x) and tells the user to run the project's publish command when ready. ## Quick Start Ask the agent to review the just-merged pull request and recommend the appropriate semver version bump level.

Frequently Asked Questions about semver

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

FAQPage Schema
How do I decide between a patch, minor, or major version bump?▼

Bug fixes and small improvements warrant a patch bump, new user-facing features warrant a minor bump, and breaking changes to public APIs, CLIs, or protocols warrant a major bump on 1.x or a minor bump while at 0.x.

What counts as a breaking change in semantic versioning?▼

Breaking changes include removing or renaming commands, flags, exported APIs, or config keys, changing input or output shapes incompatibly, or dropping support for a runtime, platform, or protocol version. Additive changes and internal refactors are not breaking.

Can breaking changes ship in a minor release on 0.x versions?▼

Yes. While a package is at 0.x, breaking changes can ship in a minor bump because the major version staying at 0 signals the project is not yet stable. Reserve 1.0.0 for when you commit to stability.

Should I include the version bump in the pull request itself?▼

No. Including the bump in the PR causes merge conflicts when multiple agents work in parallel. Instead, recommend the bump level after the PR merges and let the maintainer run the project's version bump command.

Do documentation or test-only changes need a version bump?▼

No. Internal refactors, documentation-only changes, and test-only changes do not warrant any version bump since they produce no user-facing difference in the published package.

Related Skills

Explore More Software Engineering Skills→
highflame-aihighflame-ai
4

release-notes

Generate structured release notes from git commit history and pull requests.

Official
Advanced
GenEducationGenEducation

bmad-os-release-module

Coordinate software releases with version bumps, changelog updates, git tagging, npm publishing, and GitHub release creation.

Official
Intermediate
UniClipboardUniClipboard
1.6k

gen-changelog

Generate bilingual release changelogs from Git commit history.

Official
Intermediate
marquesfelipmarquesfelip

automated-versioning

Automate semantic version bumps from conventional commits in CI/CD pipelines.

Community
Advanced