version-manager

Enforce semantic versioning, deprecation lifecycles, and migration safety checks.

Updated Sep 2, 2025
One-click install
npx skills add https://github.com/thefixer3x/onasis-gateway --skill version-manager-thefixer3x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-manager
Source: https://github.com/thefixer3x/onasis-gateway/tree/main/.claude/skills/version-manager
Command: npx skills add https://github.com/thefixer3x/onasis-gateway --skill version-manager-thefixer3x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enforces strict rules and best practices for managing software versions, preventing breaking changes, ensuring smooth migrations, and maintaining compatibility.

Core Features & Use Cases

  • Semver Validation: Ensures all version numbers adhere to semantic versioning standards.
  • Deprecation Management: Guides the process of deprecating old versions with a mandatory notice period.
  • Migration Safety: Verifies that all version transitions are handled with registered migration scripts and rollback capabilities.
  • Use Case: When a developer modifies the core versioning logic, this skill acts as a safety net, flagging any attempts to bypass semver rules, skip deprecation phases, or introduce breaking changes without proper migration paths.

Quick Start

Use the version-manager skill to review proposed changes to the versioning system.

Frequently Asked Questions about version-manager

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

FAQPage Schema
How do I enforce semantic versioning rules when modifying core versioning logic?

To enforce semantic versioning, you can apply automated guardrails that validate version numbers against semver standards and flag any attempts to bypass these rules during core versioning module modifications. This ensures strict compliance with versioning conventions.

What is the correct process for deprecating old software versions without breaking compatibility?

Deprecating old software versions requires following a mandatory notice period and specific deprecation protocols. This process ensures users are informed and compatibility is maintained before the version is fully retired, preventing unexpected breakage.

How do I ensure safe migration paths for software updates with breaking changes?

Ensuring safe migration paths requires registering dedicated migration scripts and verifying rollback capabilities before deploying software updates. This approach detects breaking changes and confirms that all version transitions are handled safely with proper fallback options.

Can I skip the deprecation phase and immediately remove an outdated version?

No, skipping the deprecation phase is blocked by deprecation protocols that require a mandatory notice period. This safety net prevents breaking changes by ensuring users have adequate time to migrate before a version is fully removed.

What are the limitations of relying on manual compatibility analysis for version transitions?

Manual compatibility analysis lacks automated breaking change detection and migration safety checks, increasing the risk of introducing unsafe version transitions. Automated guardrails are necessary to verify registered migration scripts and enforce semver validation consistently.