SkillsAdd

smithery.ai

version-bump

Manage semantic version updates for rad-mem project.

First seen Mar 20, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Summary

  • Manage semantic version updates for rad-mem project.
  • Handles patch, minor, and major version increments following semantic versioning.
  • Updates package.json, marketplace.json, plugin.json, and CLAUDE.md version number (NOT version history).
  • Creates git tags and GitHub releases.
  • Auto-generates CHANGELOG.md from releases.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

dms-schema-conversion Similar name
aws/agent-toolkit-for-aws

Handles the full DMS Schema Conversion lifecycle including creating migration projects, convert…

3.2K installs
portable-text-conversion Similar name
sanity-io/agent-toolkit

Convert HTML and Markdown content into Portable Text blocks for Sanity.

2.2K installs
doca-version Similar name
nvidia/skills

Use this skill when the user is doing DOCA version handling — detecting the installed release, …

118 installs
landing-page-conversion-audit Similar name
autonnel/autonnel-skills

Audit a landing page, sales page or checkout page for conversion leaks and return a fix list or…

44.3K installs
server-side-conversion-tracking Similar name
autonnel/autonnel-skills

Set up server-side conversion tracking so purchases are reported accurately to Facebook, TikTok…

43.5K installs
git-workflow-and-versioning Similar name
addyosmani/agent-skills

Structures git workflow practices. Use when making any code change. Use when committing, branch…

30K installs

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,075 B
  • docs SUMMARY.md 340 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 7 installs

SKILL.md

Version Bump Skill

Manage semantic versioning across the rad-mem project with consistent updates to all version-tracked files.

Quick Reference

Files requiring updates (ALL FOUR):

  1. package.json (line 3)
  2. .claude-plugin/marketplace.json (line 13)
  3. plugin/.claude-plugin/plugin.json (line 3)
  4. CLAUDE.md (line 9 ONLY - version number, NOT version history)

Semantic versioning:

  • PATCH (x.y.Z): Bugfixes only
  • MINOR (x.Y.0): New features, backward compatible
  • MAJOR (X.0.0): Breaking changes

Quick Decision Guide

What changed?

  • "Fixed a bug" → PATCH (5.3.0 → 5.3.1)
  • "Added new feature" → MINOR (5.3.0 → 5.4.0)
  • "Breaking change" → MAJOR (5.3.0 → 6.0.0)

If unclear, ASK THE USER explicitly.

Standard Workflow

See [operations/workflow.md](operations/workflow.md) for detailed step-by-step process.

Quick version:

  1. Determine version type (PATCH/MINOR/MAJOR)
  2. Calculate new version from current
  3. Preview changes to user
  4. Update ALL FOUR files
  5. Verify consistency
  6. Build and test
  7. Commit and create git tag
  8. Push and create GitHub release
  9. Generate CHANGELOG.md from releases and commit

Common Scenarios

See [operations/scenarios.md](operations/scenarios.md) for examples:

  • Bug fix releases
  • New feature releases
  • Breaking change releases

Critical Rules

ALWAYS:

  • Update ALL FOUR files with matching version numbers
  • Create git tag with format vX.Y.Z
  • Create GitHub release from the tag
  • Generate CHANGELOG.md from releases after creating release
  • Ask user if version type is unclear

NEVER:

  • Update only one, two, or three files
  • Skip the verification step
  • Forget to create git tag or GitHub release
  • Add version history entries to CLAUDE.md (that's managed separately)

Verification Checklist

Before considering the task complete:

  • All FOUR files have matching version numbers
  • npm run build succeeds
  • Git commit created with all version files
  • Git tag created (format: vX.Y.Z)
  • Commit and tags pushed to remote
  • GitHub release created from the tag
  • CHANGELOG.md generated and committed
  • CLAUDE.md: ONLY line 9 updated (version number), NOT version history

Reference Commands

# View current version
grep '"version"' package.json

# Verify consistency across all version files
grep '"version"' package.json .claude-plugin/marketplace.json plugin/.claude-plugin/plugin.json

# View git tags
git tag -l -n1

# Check what will be committed
git status
git diff package.json .claude-plugin/marketplace.json plugin/.claude-plugin/plugin.json CLAUDE.md

For more commands, see [operations/reference.md](operations/reference.md).