semantic-versioning

Enforce semantic versioning and update SKILL.md version entries with backups.

Updated Apr 8, 2026

Search Tags:#automation #versioning #semver #scripts #release-management #semantic-versioning

Ready to run

npx skills add https://github.com/isaackehle/skills --skill semantic-versioning-isaackehle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: semantic-versioning
Source: https://github.com/isaackehle/skills/tree/main/semantic-versioning
Command: npx skills add https://github.com/isaackehle/skills --skill semantic-versioning-isaackehle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates inconsistent or incorrect version numbers by enforcing semantic versioning rules and providing tools to update SKILL.md version fields reliably.

Core Features & Use Cases

Automated version bumps: Interactive scripts to increment major, minor, or patch versions according to semver rules.
Safe updates: File backups and confirmation prompts to reduce accidental overwrites of SKILL.md.
Repository integration: Guidance and tooling for maintaining consistent versions across a skills repository during releases and commits.
Use Case: A maintainer preparing a backward-compatible feature can run the updater to bump the minor version and automatically persist the change in SKILL.md.

Quick Start

Run the version updater in the skill directory and confirm the prompt to increment the appropriate semantic version.

Frequently Asked Questions about semantic-versioning

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

FAQPage Schema

How do I update semantic versioning in a SKILL.md file?▼

To update semantic versioning in a SKILL.md file, you run the interactive version updater in the skill directory, select the appropriate major, minor, or patch increment, and confirm the prompt to safely persist the change with automatic backups.

What is the best way to automate version bumps for a multi-skill repository?▼

Automating version bumps for a multi-skill repository is handled by applying semantic versioning rules during release and maintenance tasks, ensuring consistent release numbers across individual skills through interactive scripts and safe in-place file updates.

Can I safely increment project release versions without losing file data?▼

Yes, you can safely increment project release versions because the updater creates file backups and requires confirmation prompts before applying in-place updates, which reduces accidental overwrites of your SKILL.md entries.

How does semantic version parsing work for backward-compatible features?▼

Semantic version parsing for backward-compatible features works by enforcing semver rules to increment the minor version, accurately reading the current version string and applying the correct mathematical bump to maintain consistent release tracking.

Why do my project release numbers become inconsistent during commit maintenance?▼

Project release numbers become inconsistent during commit maintenance when semantic versioning rules are not enforced, leading to incorrect version entries that require safe in-place file updates to realign the recorded SKILL.md versions.