Semantic Versioning

Analyze commits and API diffs to compute semantic version bumps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mkolb22/zen-plugin --skill semantic-versioning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Semantic Versioning
Source: https://github.com/mkolb22/zen-plugin/tree/main/skills/semantic-versioning
Command: npx skills add https://github.com/mkolb22/zen-plugin --skill semantic-versioning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Determine the correct semantic version bump (major, minor, or patch) by analyzing commits, breaking changes, and API compatibility to ensure release accuracy and auditable history.

Core Features & Use Cases

  • Automated version bumping based on conventional commits and API diffs.
  • Breaking change detection across APIs, configurations, and data changes.
  • Monorepo support to compute bumps per package while maintaining overall coherence.

Quick Start

Run semantic version analysis on the latest commits to determine the correct major, minor, or patch bump.

Frequently Asked Questions about Semantic Versioning

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

FAQPage Schema
How do I determine the correct semantic version bump for my latest commits?

To determine the correct semantic version bump, analyze your latest commits and API diffs to identify breaking changes, new features, and fixes, which dictates whether a major, minor, or patch update is required.

How does API diff analysis decide between a major and minor version bump?

API diff analysis decides version bumps by detecting breaking changes across APIs, configurations, and data to trigger major updates, while new features trigger minor updates and fixes trigger patch updates.

Can I compute semantic versioning bumps for individual packages in a monorepo?

Yes, you can compute semantic versioning bumps for individual packages in a monorepo, calculating version updates per package while maintaining overall coherence across the multi-module project.

Do I need conventional commits to automate semantic versioning?

Using conventional commits is a core feature for automating semantic versioning, as the commit history and API diffs are analyzed together to determine the correct version bump and provide release rationale.

What is the best way to ensure release accuracy when updating library versions?

The best way to ensure release accuracy is to apply automated version bumping based on conventional commits and API compatibility, which produces an auditable history and a recommended new version with rationale.

Why does a configuration change trigger a major semantic version bump?

A configuration change triggers a major semantic version bump because breaking change detection scans APIs, configurations, and data changes, identifying any incompatible modifications that require a major update.