busic-version-management

Name: busic-version-management
Availability: InStock
Author: glowled

Enforce SemVer formatting and synchronize version data across source files and release artifacts.

23|8|Updated Mar 2, 2026

Search Tags:#changelog #versioning #publishing #metadata #semver #release-management

Ready to run

npx skills add https://github.com/GlowLED/BuSic --skill busic-version-management

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: busic-version-management
Source: https://github.com/GlowLED/BuSic/tree/main/.agents/skills/busic-version-management
Command: npx skills add https://github.com/GlowLED/BuSic --skill busic-version-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BuSic version management enforces SemVer formatting and ensures version metadata stays synchronized across release artifacts and source files.

Core Features & Use Cases

SemVer validation and version bump guidance
Synchronization of pubspec.yaml, CHANGELOG.md, and versions-manifest.json during release
Guidance for release workflows and build metadata propagation

Quick Start

Provide the new version string and let this skill validate SemVer compliance and update all related files.

Frequently Asked Questions about busic-version-management

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

FAQPage Schema

How do I synchronize version data across pubspec.yaml and CHANGELOG.md during a release?▼

To determine the correct version bump for a release, this skill evaluates your changes to provide major, minor, or patch guidance based on strict SemVer formatting rules. It analyzes your release notes alignment and validates the proposed version string before synchronizing metadata.

How does SemVer validation work for build metadata propagation in release artifacts?▼

To validate SemVer compliance before publishing, provide the new version string and the skill will check it against standard formatting rules. It validates pubspec.yaml, CHANGELOG.md, and versions-manifest.json for consistency before synchronizing the metadata across all release artifacts.

What is the best way to enforce SemVer formatting across multiple release files?▼

To align release notes with version bumps, this skill validates your SemVer compliance and synchronizes the updated metadata across CHANGELOG.md and versions-manifest.json. It ensures your release notes accurately reflect the major, minor, or patch changes applied to the version string.

Why does my versions-manifest.json show a different version than pubspec.yaml?▼

To update release files consistently during a version bump, provide the new version string and let this skill synchronize the data across pubspec.yaml, CHANGELOG.md, and versions-manifest.json. It validates SemVer compliance and propagates build metadata to ensure all artifacts match.