version-bump-advisor

Classify design system changes and recommend semantic versioning bumps.

155|7|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/murphytrueman/design-system-ops --skill version-bump-advisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-bump-advisor
Source: https://github.com/murphytrueman/design-system-ops/tree/main/skills/version-bump-advisor
Command: npx skills add https://github.com/murphytrueman/design-system-ops --skill version-bump-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the subjectivity and friction in design system versioning by providing a consistent framework for classifying changes, recommending the correct semantic versioning (semver) bump, and generating a detailed changelog entry with reasoning.

Core Features & Use Cases

  • Automated Semver Classification: Classifies changes into Breaking, Minor, or Patch categories based on strict rules.
  • Changelog Generation: Produces a markdown-formatted, copy-paste-ready changelog entry.
  • Migration Guidance: Provides specific migration notes for breaking changes.
  • Edge Case Handling: Addresses common design system versioning complexities like pre-1.0 releases, deprecations, and CSS specificity changes.
  • Use Case: When preparing a new release, provide the Skill with a git diff or a list of changes, and it will recommend the semver bump (e.g., major, minor, patch), explain the reasoning, and draft the changelog entry.

Quick Start

Use the version-bump-advisor skill to recommend a semver bump for the attached git diff output.

Frequently Asked Questions about version-bump-advisor

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

FAQPage Schema
How do I determine the correct semver bump for design system changes?

To determine the correct semver bump, you analyze git diffs or natural language descriptions to classify changes as breaking, minor, or patch. This classification directly dictates the appropriate semantic versioning increment for your release.

How do I generate markdown changelog entries from a git diff?

You can generate markdown changelog entries by providing a git diff to an automated classifier. It produces a copy-paste-ready markdown formatted changelog entry detailing the semantic versioning updates and reasoning.

What is the best way to handle versioning for pre-1.0 design system releases?

Handling versioning for pre-1.0 design system releases requires addressing specific edge cases like deprecations and CSS specificity changes. Automated semver classification evaluates these complexities to recommend the correct version bump.

Can I automate migration notes for breaking changes in a release?

Yes, you can automate migration notes for breaking changes. When evaluating git diffs, the system identifies breaking changes and provides specific migration guidance alongside the recommended semver bump and generated changelog entry.

Does automated versioning work with natural language descriptions of changes?

Automated versioning works with natural language descriptions by analyzing the provided text to categorize changes. It determines if the updates constitute a breaking, minor, or patch change to recommend the correct semver increment.