versioning

Audit versioning scheme adherence, changelog hygiene, and release flow gating.

Updated May 28, 2026
One-click install
npx skills add https://github.com/syntropic137/harness-app-template --skill versioning-syntropic137
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: versioning
Source: https://github.com/syntropic137/harness-app-template/tree/main/.claude/skills/versioning
Command: npx skills add https://github.com/syntropic137/harness-app-template --skill versioning-syntropic137

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about versioning

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

FAQPage Schema
How do I prevent manifest drift and broken builds in a polyglot monorepo?

Prevent manifest drift in a polyglot monorepo by auditing versioning scheme adherence across all language manifests to ensure versions remain in lockstep and consumer builds do not break from inconsistent versioning practices.

What is the best way to enforce SemVer or CalVer compliance for public APIs?

Enforce SemVer or CalVer compliance by validating that projects declare and consistently apply a stated versioning scheme for all publicly versioned artifacts, ensuring version bumps accurately reflect the scope of changes.

How do I audit changelog hygiene and deprecation policy compliance?

Audit changelog hygiene and deprecation policy compliance by reviewing release documentation to verify changelogs list user-visible changes and that breaking changes are preceded by deprecation warnings with documented migration paths.

Can I use release automation to gate version bumps and prevent accidental breaking changes?

Use release automation to gate version bumps by validating documented release processes to ensure appropriate quality gates exist, preventing accidental or unreviewed version cuts and surprise breaking changes.

Does versioning scheme auditing work for deployable services and public libraries?

Versioning scheme auditing works for deployable services and public libraries by applying to all publicly versioned artifacts to validate versioning contracts, public surface classification, and release flow gating.