api-contract-reviewer

You can check if API changes break existing consumers by submitting the diff to evaluate surface stability across routes, schemas, and exported types. The review flags incompatible modifications and outputs findings with recommended migration paths.

An API contract review identifies whether changes to a public API silently break existing consumers. You need it when modifying routes, JSON-RPC methods, CLI surfaces, schemas, exported types, status codes, error shapes, or auth contracts across module boundaries.

To assess breaking changes in JSON-RPC methods and schemas, provide the change set for evaluation. The review checks consumer-facing surfaces and flags incompatible modifications, enforcing compliance with versioning and deprecation strategies.

Yes, this API compatibility check covers CLI surfaces and auth contracts. It evaluates consumer-facing surfaces including routes, exported types, status codes, and error shapes across module boundaries to ensure non-migration changes require explicit versioning.

The best way to enforce API versioning and deprecation strategies is to review diffs for consumer-facing surface compatibility. This ensures non-migration changes require explicit versioning and provides recommended migrations with confidence levels for breaking changes.

When an API change is detected as breaking, the review evaluates surface stability without migration paths and flags the incompatible modifications. It then outputs findings with recommended migrations and confidence levels to guide consumer updates.