version-bump

Automates semantic version bumps across multiple tracked files and publishes GitHub releases.

90.2k|7.8k|Updated Aug 31, 2025
One-click install
npx skills add https://github.com/thedotmack/claude-mem --skill version-bump
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-bump
Source: https://github.com/thedotmack/claude-mem/tree/main/.claude/skills/version-bump
Command: npx skills add https://github.com/thedotmack/claude-mem --skill version-bump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually updating version numbers across multiple project files (package.json, marketplace.json, CLAUDE.md) is tedious and prone to errors, leading to inconsistencies that can disrupt releases. This Skill automates the entire semantic versioning process, ensuring all project metadata is perfectly synchronized.

Core Features & Use Cases

  • Automated Semantic Versioning: Handles PATCH, MINOR, and MAJOR version increments based on your project changes.
  • Multi-File Consistency: Automatically updates package.json, .claude-plugin/marketplace.json, and CLAUDE.md simultaneously.
  • Guided Release Workflow: Prompts you to determine the correct version type (MAJOR, MINOR, PATCH) and previews all changes before execution.
  • Use Case: After implementing a critical bug fix, simply tell Claude to "bump the version for a patch release." The Skill will automatically update all relevant files, generate the correct CLAUDE.md entry, and ensure your project's version numbers are perfectly aligned, saving you time and preventing release headaches.

Quick Start

User: "I've completed a new feature. Please prepare a minor version release." Claude: (Activates version-bump skill) "Current version: 4.2.8. New version will be 4.3.0 (MINOR). Files to update: package.json, marketplace.json, CLAUDE.md. Proceed? (yes/no)"

Frequently Asked Questions about version-bump

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

FAQPage Schema
How do I automate semantic version bumps across multiple project files?

Semantic versioning automation updates package.json, marketplace.json, and plugin configuration files simultaneously based on release type (PATCH, MINOR, MAJOR), ensuring all version numbers stay synchronized and eliminating manual sync errors across your project.

Can I update version numbers in package.json and marketplace.json at the same time?

Yes, this Skill updates package.json, .claude-plugin/marketplace.json, and plugin/.claude-plugin/plugin.json in lockstep during a single operation, preventing version inconsistencies between files.

What's the best way to manage version releases with git tags and GitHub releases?

Automated semantic versioning handles version computation, multi-file updates, git commits, tag creation, and GitHub release generation as a guided workflow, removing manual steps and reducing release-related errors.

How do I determine whether to use PATCH, MINOR, or MAJOR version increments?

The Skill guides you through determining the correct version type based on your changes (bug fixes trigger PATCH, new features trigger MINOR, breaking changes trigger MAJOR), then previews all changes before execution.

Does version automation work with projects tracking versions in multiple configuration files?

Yes, this Skill is designed for multi-file version tracking, simultaneously updating package.json, marketplace metadata, and plugin configuration while verifying consistency across all three files.

What happens if version numbers become inconsistent across my project files?

Automated semantic versioning prevents inconsistencies by updating all tracked files to identical versions in a single operation and verifying consistency before committing, so marketplace, package, and plugin versions always align.