version-management

Automate semantic versioning, CHANGELOG generation, and Git tagging for devloop projects.

9|2|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/Zate/cc-plugins --skill version-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-management
Source: https://github.com/Zate/cc-plugins/tree/main/plugins/devloop/skills/version-management
Command: npx skills add https://github.com/Zate/cc-plugins --skill version-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual versioning and changelog updates are error-prone and time-consuming, hindering efficient release management. This Skill automates semantic versioning, CHANGELOG generation, and Git tagging for devloop projects.

Core Features & Use Cases

  • Semantic Versioning: Apply MAJOR.MINOR.PATCH rules based on conventional commits.
  • Auto-Detection from Commits: Automatically determine the appropriate version bump by parsing commit messages since the last tag.
  • Version File Updates: Identify and update version strings in common project files (package.json, __version__.py, Cargo.toml, etc.).
  • CHANGELOG Management: Generate and update CHANGELOG.md entries following the "Keep a Changelog" format.
  • Release Workflow & Tagging: Guide through the complete release process, including creating release commits and Git tags.
  • Use Case: Determine the next version bump for a feature, update package.json and CHANGELOG.md, or create a Git release tag for a new product version.

Quick Start

Based on recent feat: and fix: commits, suggest the next semantic version bump and generate a CHANGELOG entry.

Frequently Asked Questions about version-management

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

FAQPage Schema
How do I automate semantic versioning based on my Git commits?

Semantic versioning automates version bumps (MAJOR.MINOR.PATCH) by parsing conventional commits since your last tag. This Skill detects `feat:` and `fix:` prefixes in commit messages to determine whether to increment major, minor, or patch versions, eliminating manual version decisions.

Can I automatically update version numbers across different project types?

Yes. This Skill identifies and updates version strings in language-specific files—`package.json` for JavaScript/TypeScript, `__version__.py` for Python, `Cargo.toml` for Rust, and similar files for Go—so you maintain consistent versions across your entire project.

How do I generate and maintain a CHANGELOG from commit history?

CHANGELOG generation pulls from conventional commits and formats entries in Keep a Changelog style, organizing features, fixes, and breaking changes by version. The Skill updates your existing CHANGELOG.md automatically during release workflows.

What's the best way to create Git release tags with version metadata?

This Skill guides you through the complete release process: suggest the next version bump, update version files, generate release notes, create a release commit, and tag it in Git—all coordinated so your repository history and version metadata stay in sync.

Do I need to write commit messages in a specific format for versioning to work?

Yes. Commits must follow conventional commit format (`feat:`, `fix:`, `BREAKING CHANGE:`) so the Skill can parse them and determine the correct version increment. This format is widely adopted and integrates with semantic versioning standards.

Can this work with my existing devloop release workflow?

This Skill integrates directly into devloop: it runs during phase completion and when you use `/devloop:ship` to trigger feature shipping, automating versioning and tagging as part of your standard release process.