version-semver-product

Determine semantic version bumps and generate Git tags for product releases.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/cslsoftwares/ParamentersORM --skill version-semver-product
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-semver-product
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/version-semver-product_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill version-semver-product

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces semantic versioning for product releases by determining the correct MAJOR/MINOR/PATCH bump and generating the corresponding version tag, ensuring release consistency across the product.

Core Features & Use Cases

  • Automated version bump decision: Determines MAJOR, MINOR, or PATCH based on changes and their impact on the public API.
  • Version history updates: Updates VERSION.md and adds an entry to CHANGELOG.md for each release.
  • Tag generation: Creates a Git tag in the format vX.Y.Z for the release.

Quick Start

Run the skill with the current version and release description to compute the next SemVer bump and apply the updates.

Frequently Asked Questions about version-semver-product

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

FAQPage Schema
How do I determine the correct semantic version bump for a product release?

To determine the correct semantic version bump, you analyze changes and their impact on the public API to decide between a MAJOR, MINOR, or PATCH update, ensuring release consistency across your product boundary.

How do I update CHANGELOG.md and VERSION.md when creating a release tag?

You can update version history by applying the computed semantic version bump to VERSION.md and adding a corresponding release entry to CHANGELOG.md, which records the version history for your product.

Does this skill generate Git tags in the vX.Y.Z format for semantic versioning?

Yes, semantic versioning tag generation creates a Git tag in the standard vX.Y.Z format based on the determined MAJOR, MINOR, or PATCH bump for your product release.

When should I use a MAJOR versus a MINOR semantic version bump?

You trigger a MAJOR semantic version bump when changes break the public API, whereas a MINOR bump applies when adding backward-compatible functionality within your product boundary.

Can I automate release management by computing the next SemVer bump from release descriptions?

Yes, you can automate release management by providing the current version and release description to compute the next SemVer bump, which then automatically applies updates to version history files.

Do I need to manually edit VERSION.md before generating a Git tag for a new release?

No, manual edits to VERSION.md are unnecessary because the skill automatically updates version history files and creates the Git tag after determining the correct semantic version bump from your release description.