← ClaudeAtlas

graphql-schema-regressionlisted

Use for any question about whether a GraphQL schema change is safe, including one pasted diff and a field change that broke a client: diffs schemas with graphql-inspector, classifies changes as breaking, dangerous or safe (removed fields, narrowed types, deprecated-field removal with usage checks), checks Federation supergraph drift and gates CI.
testland/qa-skills · ★ 0 · API & Backend · score 72
Install: claude install-skill testland/qa-skills
# graphql-schema-regression ## Overview GraphQL Inspector is a schema-management CLI from The Guild that validates GraphQL schemas and detects changes between two versions ([gqi-overview][overview]). It classifies every change into one of three tiers ([gqi-diff][diff]): | Classification | Meaning | |----------------|--------------------------------------------------------------------| | **Breaking** | Will disrupt existing clients (removed fields, narrowed types). | | **Dangerous** | Won't immediately break clients but may cause issues (e.g. union member added). | | **Non-breaking** | Safe additions (new fields on existing types, new types). | [overview]: https://the-guild.dev/graphql/inspector [diff]: https://the-guild.dev/graphql/inspector/docs/essentials/diff The tool exits non-zero when breaking changes exist, exits zero otherwise - the gate is the exit code. This is the GraphQL-specific counterpart to `openapi-contract-diff`. Use it when the API surface is GraphQL (single schema or Apollo Federation supergraph) instead of REST. ## When to use - The repo defines a GraphQL schema (`schema.graphql`, an SDL string in code, or a Federation subgraph). - The team wants a CI gate on schema regressions between the PR and the deployed schema. - The team uses **deprecated field tracking** (`@deprecated`) and wants `suppressRemovalOfDeprecatedField` semantics - i.e. removing a field that has been