versioning

Bump semantic versions and update changelog entries via bash script.

2|1|Updated Nov 13, 2025
One-click install
npx skills add https://github.com/MolcajeteAI/plugin --skill versioning-molcajeteai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: versioning
Source: https://github.com/MolcajeteAI/plugin/tree/main/.claude/skills/versioning
Command: npx skills add https://github.com/MolcajeteAI/plugin --skill versioning-molcajeteai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill standardizes the process of version bumping and changelog updates for software projects, ensuring consistency and clarity in release management.

Core Features & Use Cases

  • Semantic Versioning: Enforces MAJOR.MINOR.PATCH versioning conventions.
  • Automated Bumping: Provides a script to automate version increments.
  • Changelog Management: Guides the creation of categorized changelog entries.
  • Use Case: After releasing a new feature, use this Skill to automatically update the version number in plugin.json, then add the new feature details to the prd/changelog.md file.

Quick Start

Use the versioning skill to bump the patch version and update the changelog.

Frequently Asked Questions about versioning

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

FAQPage Schema
How do I automate semantic versioning and changelog updates?

Semantic versioning is a convention that assigns MAJOR, MINOR, and PATCH version numbers to communicate the type of changes in a software release. It helps maintain consistency and clarity in release management.

How does automated version bumping work for release management?

Automated version bumping uses a bash script to increment the MAJOR.MINOR.PATCH version number in project files like plugin.json, ensuring consistent release management without manual edits.

Can I use this semantic versioning skill with my existing markdown changelog?

Yes, you can use this skill with a markdown changelog file, as it guides the creation of categorized changelog entries to maintain consistent release documentation.

What's the best way to structure changelog entries for software releases?

The best way to manage changelog entries is by categorizing them according to semantic versioning conventions within a markdown file, ensuring clear and consistent release documentation.

When do I need to apply semantic versioning conventions in software development?

You need to apply semantic versioning conventions in software development workflows requiring consistent release management, specifically when updating version numbers and documenting changes.