version-bumper

Automate synchronized version bumps and changelog updates across Python modules, READMEs, docs, and badges.

Updated Mar 20, 2026

Search Tags:#automation #changelog #documentation #release #patch #version

Ready to run

npx skills add https://github.com/msulikowski96-cmd/webui --skill version-bumper-msulikowski96-cmd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: version-bumper
Source: https://github.com/msulikowski96-cmd/webui/tree/main/extensions/.github/skills/version-bumper
Command: npx skills add https://github.com/msulikowski96-cmd/webui --skill version-bumper-msulikowski96-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Up-to-date releases require consistent version numbers and changelog entries across code, docs, and metadata. This skill automates propagating version bumps to every relevant file to prevent drift and manual errors.

Core Features & Use Cases

Cross-file version sync: updates version numbers in Python modules, READMEs, docs, and badge references.
Changelog alignment: synchronizes What's New / 最新更新 sections with the new version.
Audit & verification: validates diffs to ensure no formatting or content is broken.

Quick Start

Execute the bump script with the target version and messages to propagate the update across all listed files.

Frequently Asked Questions about version-bumper

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

FAQPage Schema

How do I synchronize version bumps across multiple files for a release?▼

Synchronizing version bumps across multiple files requires automating version upgrades in Python modules, READMEs, docs, and badge references to prevent drift and manual errors during a release.

What is the best way to keep changelog entries aligned with new version numbers?▼

Keeping changelog entries aligned involves synchronizing What's New sections with the new version number automatically, ensuring documentation stays consistent with the updated release metadata.

Does this version bumping process require external dependencies?▼

The version bumping process requires no external dependencies beyond the repository's standard tooling, applying patches directly to target files and verifying diffs to validate content integrity.

Can I automate release documentation updates for Python modules and badges?▼

Automating release documentation updates propagates version bumps to Python modules, READMEs, docs, and badge references, ensuring metadata and documentation stay consistent across the entire project.

How do I verify that a version bump did not break file formatting or content?▼

Verifying a version bump involves validating file diffs after applying patches, ensuring no formatting or content is broken across the synchronized Python modules and documentation.

Why does version drift occur in release documentation and how is it prevented?▼

Version drift occurs when manual updates miss files across code, docs, and metadata; it is prevented by automating cross-file version sync to propagate updates consistently.