version-bump-cc

What problem does it solve?

This Skill removes the manual, error-prone work of releasing a new OmniRoute version by automatically bumping version numbers, generating a readable CHANGELOG from git history, and updating all version references across the repo and docs.

Core Features & Use Cases

• Deterministic version bumping: Applies a strict PATCH-only version policy (with a defined threshold rule) and avoids redundant bumps when the version is already updated.
• CHANGELOG generation from commits: Collects commits since the last git tag, classifies them into feature/bugfix/breaking/maintenance/test/docs/security/i18n categories, and rewrites the Unreleased section with a new versioned entry.
• Repo-wide version synchronization: Updates package.json files across workspace packages, refreshes docs/reference/openapi.yaml, updates llm.txt version references, and regenerates the lockfile.
• Documentation refresh: Reviews and updates root and docs/ files only when the generated CHANGELOG entries indicate substantive behavior changes.

Quick Start

Run the version-bump-cc workflow in your OmniRoute repo to bump PATCH version, generate a categorized CHANGELOG from commits since the last tag, and sync version references in package.json, docs, openapi.yaml, and llm.txt.