svbump

Read and write semantic versions across JSON, TOML, and YAML config files.

5|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/schpet/toolbox --skill svbump
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: svbump
Source: https://github.com/schpet/toolbox/tree/main/plugins/svbump/skills/svbump
Command: npx skills add https://github.com/schpet/toolbox --skill svbump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

svbump provides a lightweight command-line toolkit to read and write semantic versions across JSON, TOML, and YAML config files, ensuring consistent version lifecycles across projects.

Core Features & Use Cases

  • Read current versions from a variety of config formats (package.json, Cargo.toml, deno.json, etc.)
  • Write bumps (major, minor, patch) or set exact versions across files
  • Preview changes before applying to guard against accidental drift

Quick Start

svbump read version package.json svbump write patch version package.json svbump preview minor version Cargo.toml

Frequently Asked Questions about svbump

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

FAQPage Schema
How do I bump semantic versions across different config files?

Bumping semantic versions across config files involves using a CLI to read and write updates in JSON, YAML, and TOML. This skill applies major, minor, or patch changes directly to files like package.json and Cargo.toml.

Can I preview version changes in Cargo.toml before applying them?

You can preview version changes in Cargo.toml before applying them. The CLI provides a preview command to check semantic version bumps beforehand, guarding your config files against accidental drift.

Does this CLI tool support reading versions from YAML and TOML?

The CLI supports reading versions from YAML and TOML files alongside JSON. It extracts current semantic version values across these config formats to maintain consistent version lifecycles.

What is the best way to set an exact version in package.json via command line?

Setting an exact version in package.json via command line is best done using a CLI tool that writes semantic versions directly to JSON config files, ensuring precise version control without manual editing.

How do I read the current version from a deno.json file?

To read the current version from a deno.json file, execute a CLI read command targeting the file. This parses the JSON config and returns the active semantic version string for your project.

What are the limitations of using a basic CLI for version control in config files?

A limitation of using a basic CLI for version control in config files is its fundamental implementation depth, focusing strictly on reading, writing, and previewing semantic versions in JSON, TOML, and YAML without advanced automation pipelines.