Skip to content
Schemory
Skill

api-breaking-change-detector

Cross-references C# Web API controllers/DTOs against their TypeScript/JavaScript consumers (React, Angular, Vue, Svelte, Node.js, or hand-written/auto-generated HTTP clients like Fetch, Axios, NSwag) to catch contract drift in both directions: backend changes that break client applications (renamed/removed JSON keys, new required parameters, status code shifts) and frontend code sending fields the backend no longer reads. Works directly against source code, not exported OpenAPI spec files. Use when the user asks to check for breaking API changes, verify frontend/backend contract sync, or audit a DTO/controller change against its TypeScript/JS consumers before merging. Not for generating new API code from a spec (see openapi-to-application-code) or scaffolding new endpoints (see aspnet-minimal-api-openapi).

Listed from its GitHub repository. Reports from people who tried it will appear here.

Source
github/awesome-copilot
GitHub stars
41,429
License
MIT

No reports yet

Nobody has written down how api-breaking-change-detector works with their agent. Tried it? Say whether it worked, and with which agent and model.

Write the first report