What problem does it solve?
This Skill solves the risk of accidentally introducing breaking changes to APIs (protobuf, OpenAPI, GraphQL) that disrupt existing clients, cause service outages, and force unplanned, costly migrations for downstream consumers.
Core Features & Use Cases
- Multi-surface breaking change detection: Scans protobuf services, OpenAPI specs, and GraphQL schemas for incompatible changes, classifying each as wire-breaking, behavior-breaking, policy-breaking, or non-breaking.
- Policy-aware review: Aligns findings with your project's declared compatibility rules (e.g. buf WIRE_JSON policy, OpenAPI SemVer rules) to avoid false positives.
- Actionable remediation guidance: Recommends safe fixes like deprecate-then-remove cycles, version bumps, or additive alternative fields to resolve breaking changes without disrupting users.
- Use Case: A team updating a public gRPC payment service can use this Skill to flag removed proto fields or changed method signatures that would break 200+ internal client services, and get step-by-step guidance to deprecate fields safely before removal.
Quick Start
Use the review-api-compat skill to audit the API changes in your current pull request for backwards compatibility issues.