version-manager

Discover and bump semver version strings across codebase files.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/michael-conrad/.opencode --skill version-manager-michael-conrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-manager
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/version-manager
Command: npx skills add https://github.com/michael-conrad/.opencode --skill version-manager-michael-conrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discover and manage version strings across a codebase, enabling automated discovery and consistent bumps before releases.

Core Features & Use Cases

  • Dynamic discovery across multiple file formats (pyproject.toml, Cargo.toml, package.json, init.py, Chart.yaml, and more)
  • Semver-aware bumping that applies major/minor/patch changes based on changelog categories
  • Orchestrated sub-agent routing to scan and update every discovered location, ensuring consistency

Quick Start

Command the system to scan for all version strings and bump to the next release as required.

Frequently Asked Questions about version-manager

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

FAQPage Schema
How do I automate version bumping across multiple project files like pyproject.toml and package.json?

To automate version bumping across files like pyproject.toml and package.json, this Skill dynamically discovers version strings across your codebase and applies coordinated, semver-aware updates to ensure consistency before releases.

What is the best way to manage semver releases across a polyglot codebase with different configuration formats?

Managing semver releases across a polyglot codebase requires dynamic discovery of version strings in formats like Cargo.toml and Chart.yaml, followed by orchestrated sub-agent routing to scan and update every location simultaneously.

How does dynamic version discovery work without hardcoding file paths in my repository?

Dynamic version discovery works by scanning the codebase to locate version strings in common files such as __init__.py and pyproject.toml without hardcoded paths, then routing sub-agents to apply strict semver bumping rules across all discovered locations.

Can I use an automated version manager to coordinate patch and minor bumps based on my changelog categories?

Yes, you can coordinate patch and minor bumps based on changelog categories. The version manager applies semver-aware major, minor, or patch changes by orchestrating updates across all discovered version string locations in your codebase.

Does automated version string discovery support Helm Chart.yaml files along with Python and Node.js projects?

Automated version string discovery supports Chart.yaml files alongside Python and Node.js projects. It dynamically scans and manages versions across multiple file formats including pyproject.toml, package.json, Cargo.toml, and __init__.py.