version-management

Manage versions of skills, prompts, and documents with git-based tracking.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/Wesley1600/ClaudeCodeFrameWork --skill version-management-wesley1600
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-management
Source: https://github.com/Wesley1600/ClaudeCodeFrameWork/tree/main/skills/version-management
Command: npx skills add https://github.com/Wesley1600/ClaudeCodeFrameWork --skill version-management-wesley1600

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

This Skill provides git-based version control for Claude Skills, enabling semantic version tagging, changelog tracking, rollbacks, and history viewing.

Core Features & Use Cases

  • Tag releases with semantic versions (MAJOR.MINOR.PATCH)
  • Maintain changelogs and track changes to SKILL.md and scripts
  • Roll back to previous versions with safe backups
  • Compare versions and generate version reports

Quick Start

Initialize version tracking for a skill, then create a new release and tag it.

Frequently Asked Questions about version-management

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

FAQPage Schema
How do I set up semantic versioning for Claude Skills and prompts?

Semantic versioning tags releases with MAJOR.MINOR.PATCH format to track changes across SKILL.md files and scripts. Initialize version tracking for a skill, then create releases and tag them using this Skill's git-based system to maintain version directories and metadata under skills/<skill-name>/.versions.

Can I roll back a Claude Skill to a previous version?

Yes, this Skill enables safe rollbacks to previous versions with automatic backups. Compare versions and generate diffs before rolling back, ensuring you can restore earlier states of SKILL.md, scripts, and resources without data loss.

How do I maintain a changelog when releasing new versions?

Create and maintain CHANGELOG.md automatically as you tag releases with semantic versions. This Skill tracks changes to SKILL.md and scripts, documenting what changed in each version for audit trails and release notes.

What's the best way to track multiple versions of the same skill?

Use git-based version control with organized version directories under skills/<skill-name>/.versions and metadata.json for each release. Tag releases semantically and maintain diffs to compare skill iterations and manage archival.

Do I need git to use version control for Claude Skills?

Yes, git is required. This Skill implements version management through git-based tracking, leveraging git's tagging, diffs, and history capabilities to manage semantic versions, changelogs, and rollbacks.

Can I compare changes between skill versions?

Yes, generate version reports and view diffs between any two versions. This Skill compares SKILL.md files, scripts, and resources across versions to show exactly what changed between releases.