---
title: "C# / TypeScript API Contract Drift: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/github-api-breaking-change-detector/
description: "Compare C# controller and DTO contracts with TypeScript or JavaScript consumers in both directions."
---

# C# / TypeScript API Contract Drift: review, setup & limitations · Undominated.ai

> Compare C# controller and DTO contracts with TypeScript or JavaScript consumers in both directions.

[← Explore all skills](/skills/)

DEVELOPMENT WORKFLOW / GitHub community (awesome-copilot)

# C# / TypeScript API Contract Drift

Compare C# controller and DTO contracts with TypeScript or JavaScript consumers in both directions.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/github/awesome-copilot/tree/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/skills/api-breaking-change-detector)

SOURCE REVIEW

 Reviewed 2026-10-15
 Evidence 4 linked sources
 Publisher GitHub community (awesome-copilot)
 Licence [MIT ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/LICENSE)
 Revision f25421d3f1b8
 [Read what was—and wasn’t—checked ↓](#review)

“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 …”

 [GitHub community (awesome-copilot) · upstream description ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/skills/api-breaking-change-detector/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - It compares C# controller and DTO changes with TypeScript or JavaScript callers and writes a report instead of a patch.
- A missing static client is reported as not located, not as proof the endpoint is unused.
- The definition separates backend-to-client breakage from stale client-to-backend fields, and labels generated-client, normalized-route and unmatched cases.
- Locate renamed response fields still read by a client

### A good fit for

 - Reviewing a C# API change against a React, Angular, or other HTTP client in the same repo
- Locate renamed response fields still read by a client
- Review controller/DTO changes before a coordinated backend and frontend release
- Separate stale request properties ignored by the backend from response properties whose absence breaks client logic.

### Weigh up before choosing

 - The skill does not modify code.
- It does not guess a client from a similar class name.
- It does not assume camelCase unless a naming policy or JsonPropertyName is present.
- This review did not execute the resource.
- Static URL and generated-client matching can miss dynamic consumers or external clients; an unmatched route is not proof that it is unused.
- The definition uses simplified required-field rules; serializer, model-binding, validation and nullable settings must be checked for the actual framework before claiming a request will fail.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - skills/api-breaking-change-detector/SKILL.md
- README.md
- LICENSE

### Our findings

 - The process inventories C# routes and DTOs, then searches fetch, axios, and HttpClient call sites.
- No code is modified; the deliverable is a report.
- A static miss is reported as no consumer located, and the skill says not to assume the endpoint is unused.
- Property names are not paired across C# and TypeScript without a JSON naming attribute or policy.
- The definition separates backend-to-client breakage from stale client-to-backend fields, and labels generated-client, normalized-route and unmatched cases.
- Bidirectional comparison explicitly distinguishes harmless dead request fields from client reads of removed response fields; the output separately lists unmatched endpoints needing manual confirmation.

### Not established by this review

 - The resource was not executed and its tools were not called.
- No skill execution, authenticated service operation, or outcome benchmark was performed.
- Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/README.md)

DOCUMENTED COMMAND

 npx skills add github/awesome-copilot/skills/api-breaking-change-detector Copy command ↗

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

 Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

 npx skills add https://github.com/github/awesome-copilot/tree/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/skills/api-breaking-change-detector Copy reviewed-revision command ↗ - Install the pinned skill directory interactively, retaining its bundled references and scripts.
- Read controller routes and global JSON naming policy before mapping fields; include explicit JSON-name overrides and ignored properties.
- Compare old/new DTOs and client payloads, distinguish ignored extra request fields from missing response fields, and report the match method and confidence.

### Before you start

 - C# Web API source plus relevant JavaScript/TypeScript consumers
- Repository search access; no OpenAPI export is required

### Compatibility

Agents supporting directory-based SKILL.md instructions

### Local instructions; runtime access depends on the workflow

 - Read source and produce a contract-drift report; the definition explicitly does not modify code.

### Cost model

The skill is free; service usage and infrastructure can incur charges.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pinned skill definition ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/skills/api-breaking-change-detector/SKILL.md) Checked 2026-10-14 https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/skills/api-breaking-change-detector/SKILL.md Supports: summary, whySelected, bestFor, limitations, install, access, review
- [Publisher repository and installation guidance ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/README.md) Checked 2026-10-14 https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/README.md Supports: install
- [MIT licence ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/LICENSE) Checked 2026-10-14 https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/LICENSE Supports: license
- [Pinned continuation review W10 ↗](https://raw.githubusercontent.com/github/awesome-copilot/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/skills/api-breaking-change-detector/SKILL.md) Checked 2026-10-15 https://raw.githubusercontent.com/github/awesome-copilot/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/skills/api-breaking-change-detector/SKILL.md Supports: review.findings, bestFor, upstreamDescription

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Bug Reproduction Brief ↗ Reduce an uncertain bug report to an evidence-backed failing fixture before repair.](/skills/github-bug-reproduction-brief/)[### GitHub Secret Scanning Operations ↗ Configure GitHub secret detection and triage exposure with credential rotation and explicit bypass decisions.](/skills/github-secret-scanning/)[### Local Web Application Testing ↗ Exercise a running web app with Playwright and retain browser evidence for failed flows.](/skills/github-webapp-testing/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)
