API Contract Validation

Compare API contracts to classify changes and generate compatibility reports.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill api-contract-validation-strategicmilk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: API Contract Validation
Source: https://github.com/StrategicMilk/Vetinari-Orchestrastor/tree/main/vetinari/skills/catalog/worker/api-contract-validation
Command: npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill api-contract-validation-strategicmilk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Public API changes can break downstream clients; this skill detects and prevents breaking changes by comparing proposed updates to the current contract and surfacing compatibility issues.

Core Features & Use Cases

  • Contract extraction and surface comparison between current and proposed API definitions
  • Classification of changes (additive, modification, removal, rename) with breaking-change flags
  • Consumer impact analysis and migration guidance, including deprecation planning
  • Version-compatibility validation and migration path documentation for internal and external clients

Quick Start

Provide the current API contract and the proposed changes, then run the validator to generate a structured compatibility report.

Frequently Asked Questions about API Contract Validation

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

FAQPage Schema
How do I validate API changes for backward compatibility?

To validate API changes for backward compatibility, provide the current API contract and proposed changes to compare surface differences, classify modifications, and flag breaking changes impacting consumers.

What is an API contract validation and migration path report?

An API contract validation report identifies breaking changes by comparing current and proposed definitions, while the migration path details version compatibility and deprecation requirements for internal and external clients.

How do I detect breaking changes in an API modification?

Detect breaking changes in an API modification by comparing the proposed update against the current contract to classify additive, removal, and rename actions, then assessing their impact on downstream consumers.

Can I analyze consumer impact for removed API endpoints?

Yes, you can analyze consumer impact for removed API endpoints by evaluating the proposed contract changes, which flags removals and generates structured guidance for deprecation planning and client migration.

Does API contract validation work for internal and external clients?

API contract validation works for both internal and external clients by assessing the impact of additive, modification, removal, and rename changes, and documenting a version-compatibility matrix for all consumers.

When do I need to generate a deprecation plan for an API?

You need to generate a deprecation plan for an API when contract comparison identifies removal or modification changes, requiring structured migration guidance and version compatibility enforcement to prevent breaking downstream clients.