Versioning Management

Manage semantic versioning and generate Keep a Changelog changelogs.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/vertivolatam/monorepo --skill versioning-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Versioning Management
Source: https://github.com/vertivolatam/monorepo/tree/main/skills/versioning-management
Command: npx skills add https://github.com/vertivolatam/monorepo --skill versioning-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of managing semantic versioning for projects, ensuring clear and consistent tracking of changes across different components like backend and mobile applications.

Core Features & Use Cases

  • Semantic Versioning: Adheres to SemVer 2.0.0 standards (MAJOR.MINOR.PATCH).
  • Changelog Generation: Provides a standardized format for documenting changes (Added, Changed, Fixed, etc.).
  • Component Versioning: Manages versioning for distinct parts of a project (e.g., backend, mobile).
  • Use Case: Before releasing a new version of your mobile app, use this Skill to generate a CHANGELOG-v1.2.0.md file detailing all new features, bug fixes, and any breaking changes.

Quick Start

Use the versioning management skill to create a changelog for version 1.2.0.

Frequently Asked Questions about Versioning Management

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

FAQPage Schema
How do I generate a changelog following the Keep a Changelog standard?

To generate a changelog following the Keep a Changelog standard, you use this Skill to format project updates into Added, Changed, and Fixed categories, producing a structured CHANGELOG markdown file for your release.

What is semantic versioning and how do I track MAJOR, MINOR, and PATCH updates?

Semantic versioning (SemVer) tracks MAJOR, MINOR, and PATCH updates to ensure consistent release management. This Skill manages SemVer 2.0.0 standards, helping you increment version numbers based on breaking changes, new features, or bug fixes.

Can I manage versioning for distinct project components like backend and mobile apps?

Yes, you can manage versioning for distinct project components like backend and mobile applications. This Skill supports component versioning, allowing you to track semantic versions and generate changelogs independently for each part of your project.

How do I create release notes for a new mobile app version?

To create release notes for a new mobile app version, you use this Skill to compile all new features, bug fixes, and breaking changes into a standardized CHANGELOG-v1.2.0.md file detailing the update.

What is the best way to document breaking changes and bug fixes for software releases?

The best way to document breaking changes and bug fixes for software releases is using a standardized changelog format. This Skill helps you categorize updates under Added, Changed, and Fixed sections following Keep a Changelog conventions.