4 skills · sorted by relevance
Version REST and GraphQL APIs. Use when a user asks to version an API, handle breaking changes, implement API deprecation, manage multiple API versions, or design an API evolution strategy.
The English summary is being prepared. Showing the original description.
Audit a proposed API change for breaking changes — classification and impact assessment. Use when asked "is this a breaking change", "will this break clients", or "assess the impact of this API change".
The English summary is being prepared. Showing the original description.
Audit existing API for breaking change risks and missing compatibility controls. Use when asked to "find breaking change risks in our API", "audit our compatibility controls", or "what could break clients".
The English summary is being prepared. Showing the original description.
Design an API compatibility and deprecation policy — stability tiers, sunset timelines, and CI gates. Use when asked to "define an API stability policy", "set our deprecation timeline", or "write semver rules".
The English summary is being prepared. Showing the original description.