// 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.
This skill should be used when working with Restate durable execution framework, building workflows, virtual objects, or services that need automatic retries, state management, and fault tolerance. Use when the user mentions "restate", "durable execution", "durable workflows", needs to build resilient distributed systems, or when they invoke /restate.
Distill rough ideas into structured project specs with issues. This skill takes unstructured input (bullet points, rough notes, transcribed ideas) and systematically breaks it down into feature domains, identifies ambiguities requiring user clarification, and produces a single structured spec document with actionable issues. Use this skill when the user wants to transform rough project ideas into well-defined specifications and issues, or when they invoke /speccer.
Jujutsu (jj) workflow skill. This skill should be used when the project uses jj for version control instead of git. Provides guidance on using jj commands and references the jj-vcs skill for detailed documentation.
Jujutsu (jj) version control workflows and commands. Use this skill when working with jj repositories, managing changes, squashing commits, rebasing, or performing jj-specific operations.
Apple's native container runtime for macOS. Use this skill instead of Docker when running on macOS with Apple silicon. The `container` CLI provides OCI-compatible container management optimized for Apple silicon.
Manage project changelogs following the Keep a Changelog format. This skill should be used when working with CHANGELOG.md files, adding changelog entries, releasing versions, or reviewing git commits for changelog purposes.
| name | svbump |
| description | 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. |
A CLI tool for bumping semantic versions in various config file formats.
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
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 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)
Use dot notation to access nested fields:
version - Top-level version fieldpackage.version - Nested under [package] table in TOMLdependencies.foo.version - Deeply nested field# 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
Use -t or --type to override file type detection:
svbump read version config -t json
svbump write patch version config --type toml