1

    api-versioning-manager

    by Markus Isaksson

    Detect breaking API changes, recommend SemVer bumps, and generate consumer migration guides.

    Updated May 2026
    Security scanned
    One-time purchase
    branch

    $9

    One-time purchase

    ⚡ Also available via Agensi MCP — your AI agent can load this skill on demand via MCP. Learn more →

    Included in download

    • Audit branch changes for breaking API modifications before merging.
    • Generate a SemVer-compliant version bump for an upcoming release.
    • file_read, file_write automation included
    • Ready for branch
    • Instant install

    See it in action

    Recommended bump: MAJOR (v2.0.0)
    Breaking: GET /users/{id} renamed 'email' to 'email_address'.
    Impact: Consumers reading '.email' will get undefined.
    Migration: Update client models to reference 'email_address'.
    Artifacts: Generated v1-to-v2-migration.md and updated CHANGELOG.md.

    About This Skill

    Automated API Lifecycle & Breaking Change Analysis

    Ensuring backward compatibility in distributed systems is a high-stakes task. The API Versioning Manager acts as an automated compliance officer for your API evolution, performing deep structural diffs between specification versions to prevent accidental outages for your consumers.

    What it does

    This skill ingest two versions of an API specification—via file paths or Git references—and executes a comprehensive audit of every change. It categorizes modifications as breaking, additive, or non-breaking based on a strict impact rubric. Unlike simple text diffs, it understands the semantic implications of schema changes, such as narrowing field types or adding required parameters.

    • Structural Analysis: Supports OpenAPI 3.x/Swagger, GraphQL SDL, and Protobuf (proto3).
    • SemVer Enforcement: Automatically calculates the correct version bump (Major, Minor, or Patch) based on actual impact.
    • Migration Automation: Generates human-readable migration guides and updated changelogs.
    • Strategy Guidance: Recommends versioning patterns (URI, Header, or Date-based) tailored to the change set.

    Why use this skill over raw prompting?

    Prompting an LLM to "find breaking changes" often misses subtle edge cases like enum value reductions or default value shifts. This skill uses a standardized severity rubric and structured output template, ensuring consistency across your entire engineering organization. It doesn't just identify problems; it generates the documentation your consumers need to stay unblocked.

    📖 Learn more: Best Frontend & Design Skills for Claude Code →

    Use Cases

    • Audit branch changes for breaking API modifications before merging.
    • Generate a SemVer-compliant version bump for an upcoming release.
    • Create high-quality consumer migration guides automatically.
    • Maintain a historical compatibility matrix for REST and GraphQL APIs.

    Reviews

    No reviews yet - be the first to share your experience.

    Only users who have downloaded or purchased this skill can leave a review.

    Security Scanned

    Passed automated security review

    Permissions

    Read Files
    Write Files

    Diffs two API specifications and generates a changelog entry, migration guide, and compatibility matrix. Does not execute against running APIs. Does not generate new specifications — analyzes existing ones. For Protobuf, supports proto3 fully and proto2 with caveats noted in the output.

    Requires both the previous and current specification to be available. The previous version can be a file path or a git reference (tag, branch, commit) — if only a git reference is provided, the skill needs read access to the repository's history. For GraphQL projects with introspection-only setups, dump the schema to SDL first; this skill diffs SDL, not introspection responses.

    Frequently Asked Questions

    Similar Skills

    $9

    One-time