Maintains versions of skills, prompts, or documents. Provides version tagging, release management, changelogs, and rollback capabilities. Tracks changes to SKILL.md files, scripts, and resources using git-based version control with semantic versioning.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Maintains versions of skills, prompts, or documents. Provides version tagging, release management, changelogs, and rollback capabilities. Tracks changes to SKILL.md files, scripts, and resources using git-based version control with semantic versioning.
Version Management Skill
A comprehensive version management system for skills, prompts, and documents in Claude Code. This skill provides professional version control capabilities including tagging releases, maintaining changelogs, and rolling back to previous versions when needed.
Overview
This skill enables you to:
Tag releases with semantic versioning (v1.0.0, v1.1.0, etc.)
Store changelogs documenting changes between versions
Roll back to previous versions if new instructions cause errors
Track changes to SKILL.md, scripts, and resource files
Compare versions to understand what changed
Archive versions for long-term storage
Core Concepts
Version Format
Uses semantic versioning: MAJOR.MINOR.PATCH
MAJOR: Breaking changes or complete rewrites
MINOR: New features, backward compatible
PATCH: Bug fixes, minor improvements
Storage Structure
skills/<skill-name>/
├── SKILL.md # Current version
├── .versions/ # Version history
│ ├── v1.0.0/
│ │ ├── SKILL.md
│ │ ├── scripts/
│ │ └── metadata.json
│ ├── v1.1.0/
│ │ ├── SKILL.md
│ │ ├── scripts/
│ │ └── metadata.json
│ └── CHANGELOG.md # Complete change history
└── scripts/ # Current scripts
Metadata Format
Each version stores metadata in :
metadata.json
{"version":"1.0.0","timestamp":"2025-11-18T12:00:00Z","author":"Claude <noreply@anthropic.com>","commit":"abc123...","description":"Initial release with core functionality","changes":["Added version tagging","Implemented rollback mechanism","Created changelog template"],"files_tracked":["SKILL.md","scripts/version_manager.sh"]}
Workflow
1. Initialize Version Management for a Skill
Input:
Skill name or path
Initial version number (default: 0.1.0)
Actions:
Check if skill exists
Create .versions/ directory
Create initial version snapshot
Initialize CHANGELOG.md
Create metadata.json
Output:
Confirmation message with version number
Location of version storage
2. Create New Version/Tag
Input:
Skill name
Version number or bump type (major/minor/patch)
Description of changes
Optional: List of specific changes
Actions:
Validate version number format
Check if version already exists
Create version directory
Copy current SKILL.md and scripts
Generate metadata.json
Update CHANGELOG.md
Create git tag (if in git repo)
Commit changes
Output:
Version tag created: v1.2.0
Changelog entry added
Files tracked: [list]
3. List All Versions
Input:
Skill name
Optional: Filter by date range or version pattern
Actions:
Read .versions/ directory
Parse metadata.json for each version
Sort by version number or date
Format output table
Output:
Version History for 'session-start-hook':
v1.2.0 | 2025-11-18 12:00 | Added validation for linters
v1.1.0 | 2025-11-15 10:30 | Improved error handling
v1.0.0 | 2025-11-10 09:00 | Initial release
4. Show Version Details
Input:
Skill name
Version number
Actions:
Locate version directory
Read metadata.json
Display comprehensive information
Show file changes from previous version
Output:
Version: v1.2.0
Date: 2025-11-18 12:00:00Z
Author: Claude <noreply@anthropic.com>
Commit: abc123def456
Description:
Added validation for linters and improved test coverage
Changes:
- Added lint validation step
- Improved error messages
- Updated documentation
Files Modified:
- SKILL.md (+45 lines, -12 lines)
- scripts/validator.sh (new file)
5. Compare Two Versions
Input:
Skill name
Version A (e.g., v1.0.0)
Version B (e.g., v1.2.0)
Optional: Specific file to compare
Actions:
Load both versions
Perform diff on SKILL.md and scripts
Highlight changes
Show metadata differences
Output:
Unified diff format
Summary of changes
Changelog entries between versions
6. Roll Back to Previous Version
Input:
Skill name
Target version number
Optional: Create backup of current version
Actions:
CRITICAL: Create backup of current state
Verify target version exists
Confirm rollback with user
Copy files from target version to current
Update metadata
Log rollback in CHANGELOG
Create git commit
Output:
Rollback successful: v1.2.0 → v1.0.0
Backup created at: .versions/backup-2025-11-18-120000/
Changes reverted: [list]
Safety Checks:
Always create backup before rollback
Require explicit confirmation
Verify file integrity
Test rolled-back version if possible
7. Update Changelog
Input:
Skill name
Version number
Change entries
Optional: Category (Added/Changed/Fixed/Removed)
Actions:
Read current CHANGELOG.md
Add new entries under version heading
Format according to Keep a Changelog standard
Update timestamp
Save changes
Output:
Changelog updated for version v1.2.0
3 entries added under "Added" category
8. Export Version Archive
Input:
Skill name
Version number or "all"
Output format (tar.gz/zip)
Destination path
Actions:
Collect version files
Include metadata and changelog
Create archive
Verify integrity
Generate checksum
Output:
Archive created: session-start-hook-v1.2.0.tar.gz
Size: 45 KB
SHA256: abc123...
Location: /path/to/archive
Change Detection
The skill automatically tracks changes to:
Monitored Files
SKILL.md: Main skill definition
scripts/: All executable scripts
templates/: Template files
resources/: Additional resources
Change Types Detected
Content changes: Line additions/deletions
New files: Files added to skill directory
Deleted files: Files removed
Renamed files: File moves/renames
Permission changes: Executable bit changes
Detection Method
# Compare against previous version
git diff v1.0.0..v1.1.0 -- skills/skill-name/
# Track specific files
git log --follow -- skills/skill-name/SKILL.md
Error Recovery
Common Issues and Solutions
Issue: Rollback fails due to corrupted version
Solution:
Check .versions/ directory for intact versions
Use next-most-recent stable version
Restore from git history if available
Issue: Version tag already exists
Solution:
List existing versions
Increment version number
Or use --force flag to overwrite (dangerous)
Issue: Changelog merge conflict
Solution:
Export current changelog
Restore from version history
Manually merge entries
Validate format
Integration with Git
Git Tag Creation
# Create annotated tag
git tag -a v1.2.0 -m "Version 1.2.0: Added validation"# Push tag to remote
git push origin v1.2.0
Branch-Based Versioning
Development: claude/version-mgmt-<session-id>
Releases: Tagged commits on main branch
Hotfixes: Patch version bumps
Commit Messages
feat(version-mgmt): Add rollback capability
- Implement version rollback with safety checks
- Add backup creation before rollback
- Update changelog automatically
Version: v1.2.0
Skill: version-management
User: I've created a new skill called 'code-reviewer'. Please version it.
Claude: I'll initialize version management for the 'code-reviewer' skill.
1. Creating version structure
2. Taking initial snapshot as v0.1.0
3. Initializing CHANGELOG.md
4. Creating metadata
✓ Version v0.1.0 created for 'code-reviewer'
✓ Tracking: SKILL.md, scripts/reviewer.sh
✓ Changelog initialized
Next steps:
- Make improvements to your skill
- When ready, create v1.0.0 for first stable release
Scenario 2: Create Release After Updates
User: I've updated the code-reviewer skill. Tag it as v1.0.0.
Claude: I'll create version v1.0.0 for 'code-reviewer'.
Detected changes:
- SKILL.md: +67 lines, -23 lines
- scripts/reviewer.sh: +145 lines (new)
- scripts/analyzer.py: +89 lines (new)
Please provide a description of changes:
User: Added Python code analysis and improved markdown documentation
Claude: Creating version v1.0.0...
✓ Version snapshot created
✓ Metadata saved
✓ Changelog updated
✓ Git tag created: v1.0.0
Version v1.0.0 Summary:
- Description: Added Python code analysis and improved markdown documentation
- Files tracked: 3
- Total changes: +301 lines, -23 lines
- Date: 2025-11-18 12:30:00Z
Scenario 3: Rollback After Error
User: The new version v1.1.0 is causing errors. Roll back to v1.0.0.
Claude: I'll initiate rollback from v1.1.0 to v1.0.0 for 'code-reviewer'.
⚠️ WARNING: This will replace current files with v1.0.0
Rollback plan:
1. Create backup of current state
2. Restore files from v1.0.0
3. Update metadata
4. Log rollback in changelog
5. Create git commit
Proceed with rollback? (yes/no)
User: yes
Claude: Executing rollback...
✓ Backup created: .versions/backup-2025-11-18-123000/
✓ Files restored from v1.0.0
✓ SKILL.md restored
✓ scripts/ restored
✓ Metadata updated
✓ Changelog entry added
✓ Git commit created
Rollback successful!
Current version: v1.0.0
Backup location: .versions/backup-2025-11-18-123000/
You can now fix the issues and create v1.1.1.
Scenario 4: Compare Versions
User: Show me what changed between v1.0.0 and v1.2.0
Claude: Comparing versions v1.0.0 and v1.2.0 for 'code-reviewer'...
Version Metadata:
v1.0.0 (2025-11-18) → v1.2.0 (2025-11-20)
Changelog Entries:
[1.1.0] - 2025-11-19
Added: Error recovery mechanisms
Fixed: File permission handling
[1.2.0] - 2025-11-20
Added: Version comparison feature
Changed: Improved validation logic
File Changes:
SKILL.md:
+89 lines, -34 lines
scripts/reviewer.sh:
+45 lines, -12 lines
scripts/comparator.sh:
+156 lines (new file)
Total: +290 lines, -46 lines across 3 files
Security Considerations
File Integrity
SHA256 checksums for version archives
Verify file integrity before rollback
Detect tampering in version history
Permissions
Preserve file permissions in versions
Restore correct permissions on rollback
Validate script execution permissions
Backup Safety
Always create backup before destructive operations
Store backups with timestamp
Automatic cleanup of old backups (optional)
Performance Optimization
Large Skills
Incremental backups (store diffs instead of full copies)
Compression for version archives
Lazy loading of version metadata
Storage Management
Configurable retention policy
Auto-archive old versions
Cleanup of orphaned versions
Validation & Testing
Before finalizing a version:
Syntax validation: Verify YAML frontmatter
File integrity: Check all tracked files exist
Metadata completeness: Ensure all required fields
Changelog format: Validate Keep a Changelog format
Git consistency: Verify git tags match version numbers
Rollback test: Verify rollback to previous version works
Troubleshooting
Version Not Found
# List all versionsls -la skills/<skill-name>/.versions/
# Check git tags
git tag -l "v*"
Corrupted Metadata
# Regenerate from git history
git log --follow -- skills/<skill-name>/SKILL.md
Rollback Failed
# Restore from backupcp -r .versions/backup-*/ ./
Summary
The version-management skill provides professional version control for Claude Code skills, enabling:
