contract-compatibility-gate
Installation
SKILL.md
contract-compatibility-gate
Overview
Modern services rarely speak just one protocol. A single deployment might depend on Pact verifications (consumer/provider HTTP), OpenAPI compatibility for an external REST surface, GraphQL schema regressions for a public graph, and Protobuf breaking-change checks for internal gRPC. Each tool has its own exit code, its own severity levels, and its own concept of "breaking":
| Tool | Verdict surface |
|---|---|
Pact can-i-deploy |
Exit 0 = yes / 1 = no ([can-i-deploy][cid]) |
oasdiff breaking |
Exit driven by --fail-on ERR/WARN/INFO ([oasdiff-breaking][oasdiff]) |
graphql-inspector diff |
Non-zero on BREAKING; zero on DANGEROUS / NON_BREAKING ([gqi-diff][gqi]) |
buf breaking |
Non-zero on any rule violation in active categories ([buf-breaking][buf]) |