Can it block deployments if an API change is dangerous?

Yes, the skill can be configured to flag violations and suggest blocking deployments if breaking changes are detected without a corresponding major version bump.

How does it identify a 'breaking' change?

It identifies removals of endpoints or fields, changes in data types, new required fields, and enum value deletions that would cause existing clients to fail.

What protocols does this skill support?

It supports REST (via OpenAPI/Swagger), GraphQL (via GraphQL-Inspector), and gRPC (via Buf/Protobuf).

Does it support consumer-driven contract testing?

Absolutely. It integrates with industry-standard tools like Pact and Spring Cloud Contract to verify that changes won't break specific downstream consumers.

Is there a summary report generated for the team?

Yes, the skill generates a detailed Markdown compatibility report including an executive summary, severity levels, and specific recommendations for migration.

API Contract Regression Guard

Name: API Contract Regression Guard
Author: jmagly

byjmagly

•

102

•

API Development

Detects and prevents breaking changes across REST, GraphQL, and gRPC interfaces to ensure backward compatibility.

This skill automates the detection of API contract regressions by comparing current schemas against established baselines. It meticulously analyzes OpenAPI, GraphQL, and Protobuf definitions to identify breaking changes such as removed fields, type mismatches, or changed constraints. Beyond simple diffing, it validates Semantic Versioning compliance, integrates with consumer contract testing tools like Pact, and generates detailed impact reports, making it an essential tool for teams managing microservices and public-facing APIs.

Key Features

01Automated classification of changes as breaking, non-breaking, or deprecated

02Integration with consumer contract testing frameworks like Pact and Spring Cloud Contract

03102 GitHub stars

04Multi-protocol support for REST (OpenAPI), GraphQL, and gRPC (Protobuf)

05Comprehensive compatibility reporting with migration paths and consumer impact analysis

06Semantic Versioning (SemVer) validation and enforcement

Use Cases

01Preventing accidental breaking changes during pull requests and CI/CD pipelines

02Validating microservice updates against real-world consumer expectations

03Automating version bump decisions based on actual schema modifications

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jmagly/aiwg regression-api-contract

For use in Claude.ai and ChatGPT

Key Features

01Automated classification of changes as breaking, non-breaking, or deprecated

02Integration with consumer contract testing frameworks like Pact and Spring Cloud Contract

03102 GitHub stars

04Multi-protocol support for REST (OpenAPI), GraphQL, and gRPC (Protobuf)

05Comprehensive compatibility reporting with migration paths and consumer impact analysis

06Semantic Versioning (SemVer) validation and enforcement

Use Cases

01Preventing accidental breaking changes during pull requests and CI/CD pipelines

02Validating microservice updates against real-world consumer expectations

03Automating version bump decisions based on actual schema modifications

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jmagly/aiwg regression-api-contract

For use in Claude.ai and ChatGPT