Can it read my git history?

The skill provides specific git commands to analyze logs between the current HEAD and the last tag, ensuring no changes are missed during the evaluation.

How does this skill determine a version bump?

It evaluates your codebase changes against a decision tree to identify breaking API changes (MAJOR), new backward-compatible features (MINOR), or bug fixes (PATCH).

Does it support pre-1.0 versioning?

Yes, it includes specific logic for versions under 1.0.0, where breaking changes are often handled in minor updates and patch updates include small features.

Which files does it help update?

It specifically targets version updates in Cargo.toml (for Rust projects) and helps structure new version entries in CHANGELOG.md files.

Why is SemVer important for my project?

Semantic Versioning communicates the nature of changes to users, preventing 'dependency hell' by clearly signaling when updates might break existing implementations.

Semantic Versioning Manager

Name: Semantic Versioning Manager
Author: rust-works

byrust-works

•

Deployment & DevOps

Guides the process of determining appropriate semantic version bumps based on code changes and breaking API updates.

About

The Semantic Versioning Manager skill provides a structured framework for managing software releases by applying Semantic Versioning (SemVer) principles. It enables Claude to analyze git history, identify breaking changes, and recommend whether a project requires a MAJOR, MINOR, or PATCH update. By standardizing the decision-making process, it ensures consistent release cycles and accurate documentation, helping developers maintain clear communication regarding API stability and backward compatibility.

Key Features

Tailored guidance for pre-1.0 versioning flexibility
Identification of breaking API changes and backward-compatible fixes
1 GitHub stars
Support for updating version strings in Cargo.toml and CHANGELOG.md
Git log analysis to identify changes since the last release tag
Automated SemVer decision tree for Major, Minor, and Patch updates

Use Cases

Evaluating PRs to see if they necessitate a major version bump
Determining the correct version number for a new production release
Automating the synchronization of versioning across config files and documentation

About

Key Features

Tailored guidance for pre-1.0 versioning flexibility
Identification of breaking API changes and backward-compatible fixes
1 GitHub stars
Support for updating version strings in Cargo.toml and CHANGELOG.md
Git log analysis to identify changes since the last release tag
Automated SemVer decision tree for Major, Minor, and Patch updates

Use Cases

Evaluating PRs to see if they necessitate a major version bump
Determining the correct version number for a new production release
Automating the synchronization of versioning across config files and documentation