How do I install the Svbump skill?

Run npx skillmds@latest add schpet/svbump in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Svbump safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Svbump?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Svbump free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Svbump?

schpet (@schpet) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Svbump by schpet — Agent Skill

Name: Svbump
Author: schpet

Svbump

Read and write semantic versions in config files (JSON, TOML, YAML). This skill should be used when bumping versions in package.json, Cargo.toml, deno.json, or other config files, or when reading version values from these files.

schpet 47fdc2d 2.3 KB Updated Sep 17, 2026

File contents

svbump

A CLI tool for bumping semantic versions in various config file formats.

Supported Formats

JSON (package.json, deno.json, etc.)
TOML (Cargo.toml, pyproject.toml, etc.)
YAML (app.yaml, etc.)

Commands

Read Version

Print the current version to stdout:

svbump read <SELECTOR> <FILE>

Examples:

svbump read version package.json
svbump read package.version Cargo.toml
svbump read version deno.json

Write Version

Modify the version in a file:

svbump write <LEVEL> <SELECTOR> <FILE>

Level options:

major - Bump major version (1.0.0 -> 2.0.0)
minor - Bump minor version (1.0.0 -> 1.1.0)
patch - Bump patch version (1.0.0 -> 1.0.1)
X.Y.Z - Set specific version (must be higher than current)

Examples:

# Bump patch version
svbump write patch version package.json

# Bump minor version in nested field
svbump write minor package.version Cargo.toml

# Set specific version
svbump write 2.5.0 version package.json

# Copy version from one file to another
svbump write "$(svbump read version deno.json)" package.version dist-workspace.toml

Preview Version

Preview what a bump would do without modifying the file:

svbump preview <LEVEL> <SELECTOR> <FILE>

Example:

svbump preview minor version package.json
# Outputs: 1.1.0 (without modifying the file)

Selector Syntax

Use dot notation to access nested fields:

version - Top-level version field
package.version - Nested under [package] table in TOML
dependencies.foo.version - Deeply nested field

Common Workflows

Release workflow with changelog

# Set version from changelog's latest release
svbump write "$(changelog version latest)" version deno.json

# Sync version to other config files
svbump write "$(svbump read version deno.json)" package.version dist-workspace.toml

Force file type

Use -t or --type to override file type detection:

svbump read version config -t json
svbump write patch version config --type toml

---name: svbumpdescription: Read and write semantic versions in config files (JSON, TOML, YAML). This skill should be used when bumping versions in package.json, Cargo.toml, deno.json, or other config files, or when reading version values from these files.---# svbumpA CLI tool for bumping semantic versions in various config file formats.## Supported Formats- JSON (package.json, deno.json, etc.)- TOML (Cargo.toml, pyproject.toml, etc.)- YAML (app.yaml, etc.)## Commands### Read VersionPrint the current version to stdout:```svbump read <SELECTOR> <FILE>```**Examples:**```shsvbump read version package.jsonsvbump read package.version Cargo.tomlsvbump read version deno.json```### Write VersionModify the version in a file:```svbump write <LEVEL> <SELECTOR> <FILE>```**Level options:**- `major` - Bump major version (1.0.0 -> 2.0.0)- `minor` - Bump minor version (1.0.0 -> 1.1.0)- `patch` - Bump patch version (1.0.0 -> 1.0.1)- `X.Y.Z` - Set specific version (must be higher than current)**Examples:**```sh# Bump patch versionsvbump write patch version package.json# Bump minor version in nested fieldsvbump write minor package.version Cargo.toml# Set specific versionsvbump write 2.5.0 version package.json# Copy version from one file to anothersvbump write "$(svbump read version deno.json)" package.version dist-workspace.toml```### Preview VersionPreview what a bump would do without modifying the file:```svbump preview <LEVEL> <SELECTOR> <FILE>```**Example:**```shsvbump preview minor version package.json# Outputs: 1.1.0 (without modifying the file)```## Selector SyntaxUse dot notation to access nested fields:- `version` - Top-level version field- `package.version` - Nested under `[package]` table in TOML- `dependencies.foo.version` - Deeply nested field## Common Workflows### Release workflow with changelog```sh# Set version from changelog's latest releasesvbump write "$(changelog version latest)" version deno.json# Sync version to other config filessvbump write "$(svbump read version deno.json)" package.version dist-workspace.toml```### Force file typeUse `-t` or `--type` to override file type detection:```shsvbump read version config -t jsonsvbump write patch version config --type toml```

Frequently asked questions