skills.rest
christianearle01
christianearle01COMMUNITY
Explore all skills by this author →
GitHub

version-management

Validate version consistency across version.json, CLAUDE.md, README.md, SETUP_CONTEXT.md, and CHANGELOG.

Updated Dec 4, 2025
Search Tags:#automation#documentation#release-management#CHANGELOG#version-control#version-sync
One-click install
npx skills add https://github.com/christianearle01/claude-config-template --skill version-management-christianearle01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: version-management
Source: https://github.com/christianearle01/claude-config-template/tree/main/.claude/skills/version-management
Command: npx skills add https://github.com/christianearle01/claude-config-template --skill version-management-christianearle01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps version numbers and release metadata in sync across version.json, CLAUDE.md, README.md, SETUP_CONTEXT.md, and CHANGELOG to prevent release drift and confusion.

Core Features & Use Cases

  • Automatic activation: Triggers when users ask about version updates, version sync, or what files need updating for a release.
  • Verification: Compares seven known locations (version.json, CLAUDE.md, README.md lines 306, 339, 463, SETUP_CONTEXT.md lines 21, 437) to ensure all reflect the target version.
  • Guidance: Lists remaining tasks (e.g., CHANGELOG entry) and suggests next steps to complete a release.

Quick Start

  • Run: ./scripts/sync-version.sh after bumping version.json
  • Then ask: "Is version synced?" to confirm all files show the same version.

Frequently Asked Questions about version-management

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

FAQPage Schema
How do I keep version numbers in sync across multiple markdown and json files?▼

To keep version numbers in sync across files, this Skill compares version.json against CLAUDE.md, README.md, SETUP_CONTEXT.md, and CHANGELOG to detect drift and confirm all locations match the target release version.

What files need updating when planning a release?▼

When planning a release, you must update version.json, CLAUDE.md, README.md, SETUP_CONTEXT.md, and the CHANGELOG to prevent release drift and metadata confusion.

How do I verify version sync consistency after bumping the version?▼

To verify version sync consistency, run the sync-version.sh script after bumping version.json, then ask if the version is synced to confirm all seven known file locations reflect the same number.

Can I automate detecting missing CHANGELOG entries during release checks?▼

You can automate detecting missing CHANGELOG entries during routine release checks by triggering this Skill to surface missing updates and list remaining metadata synchronization tasks.

Does version sync work without a master version.json file?▼

Version sync does not work without the version.json master file, which is required as the baseline to validate and enforce consistency across associated docs like README and SETUP_CONTEXT.

Why does my README show a different version than my CHANGELOG?▼

Your README shows a different version than your CHANGELOG due to release drift; this Skill detects mismatches at specific README lines and guides you to align all files with version.json.

Related Skills

Explore More Software Engineering Skills→
hiivmindhiivmind

pr-version-bump

Analyze git changes since main to determine a semantic version bump.

Official
Advanced
nklischnklisch
7

release

Draft changelog entries from commits and execute the project's release process.

Community
Advanced
Boise-State-DevelopmentBoise-State-Development
16

version

Bump the VERSION file and sync package manifests for consistent SemVer.

Official
Intermediate
Axel051171Axel051171
33

uft-release

Automate version bumping, CHANGELOG updates, pre-release checks, and git tagging for UnifiedFloppyTool releases.

Community
Intermediate