What problem does it solve?
Poorly disciplined versioning leads to broken consumer builds, surprise breaking changes, drifted manifest versions across project files, and unclear release processes that erode trust in version numbers as a stability signal.
Core Features & Use Cases
- Versioning Scheme Auditing: Validates that projects declare and consistently apply a stated versioning scheme (SemVer, CalVer, or ZeroVer) for all publicly versioned artifacts.
- Release Hygiene Checks: Audits changelog quality, deprecation policy compliance, public API surface classification, and version bump automation to prevent manifest drift and undocumented breaking changes.
- Release Flow Validation: Reviews documented release processes to ensure appropriate gating exists to prevent accidental or unreviewed version cuts.
- Use Case: For a polyglot monorepo with packages in JavaScript, Rust, and Python, use this skill to audit that all manifest versions are in lockstep, changelogs list user-visible changes, and breaking changes are preceded by deprecation warnings with documented migration paths.
Quick Start
Use the versioning skill to audit your project's versioning practices, changelog hygiene, and release flow for compliance with industry best practices.