Evolve GraphQL schemas with intentional nullability, pagination and backward compatibility decisions.
Editorial review checked 2026-10-29 against this instruction snapshot. Supporting scripts and runtime behavior remain outside this editorial review.
The guide treats a schema as a client-facing contract, covering type design, input objects, mutation structure and evolution. It distinguishes storage internals from the API surface. This is useful for changes where adding a field seems harmless but required arguments or nullability can break existing consumers.
API designers reviewing a new schema or changing a GraphQL contract already used by applications.
Schema style rules cannot determine the correct domain model without client requirements. Changing input requirements, enum values or null behavior can affect generated clients, while deprecation notices alone do not establish whether an old field is safe to remove.
Any GraphQL implementation (Apollo Server, graphql-js, Yoga, etc.)
Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.
npx skills add https://github.com/apollographql/skills/tree/9dda1397730370aeb8df4ff8f2015c34c86b5003/skills/graphql-schema --skill graphql-schemaReview pinned skill folder ↗ · CLI documentation ↗
After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.
Static review only. This is not a security audit or a guarantee of safety.
SKILL.md text only; scripts, dependencies and runtime behavior not audited.
No configured text patterns matched. Unmatched or concealed behavior can still exist.
Allowed tools declaration: Bash(npm:*) Bash(npx:*) Read Write Edit Glob Grep. Runtime permissions and network behavior: Unknown.
85/100 · Metadata coverage 100% · Model 1.0
Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.
Identify actual consumers and representative operations, define stable identifiers and choose input and output contracts deliberately. Prefer additive changes where possible, document pagination and error semantics and separate deprecation planning from immediate field removal.
Run schema compatibility checks against the deployed contract and execute representative old and new operations. Include empty pages, missing values and validation failures, inspect generated client changes and retain evidence of consumer migration before removing previously supported behavior.
Related by category; compare scope and dependencies before choosing an alternative.
Explore brainstorming as a development workflow from obra/superpowers. Compare its source, maintenance and review signals before choosing it for your agent.
Repository star change: +1264 over 41.38 hours. 2026-10-31
Explore receiving code review as a development workflow from obra/superpowers. Compare its source, maintenance and review signals before choosing it for your agent.
Repository star change: +1264 over 41.38 hours. 2026-10-31
Explore requesting code review as a development workflow from obra/superpowers. Compare its source, maintenance and review signals before choosing it for your agent.
Repository star change: +1264 over 41.38 hours. 2026-10-31
Integrate Apollo Client with React using framework-specific data loading and cache behavior.
Repository star change: +1 over 40.37 hours. 2026-10-31
Explore apollo connectors as a development workflow from apollographql/skills. Compare its source, maintenance and review signals before choosing it for your agent.
Repository star change: +1 over 40.37 hours. 2026-10-31
Model federated GraphQL entities and shared fields with explicit subgraph ownership and composition checks.
Repository star change: +1 over 40.37 hours. 2026-10-31