graphql

Validate GraphQL schema edits for scalar rules and codegen readiness.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/flesler/dotfiles --skill graphql-flesler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphql
Source: https://github.com/flesler/dotfiles/tree/main/home/.cursor/skills/graphql
Command: npx skills add https://github.com/flesler/dotfiles --skill graphql-flesler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers modify GraphQL schemas safely by enforcing scalar usage, consistent typing, and best practices to prevent breaking changes when editing *.graphql files.

Core Features & Use Cases

  • Scalar and type validation: ensures correct scalar usage (e.g., NonEmptyString, Email, etc.) and avoids nullable pitfalls.
  • Naming and structure guidance: follows standard GraphQL patterns for queries, mutations, inputs, and payloads.
  • Codegen readiness: aligns changes with codegen requirements and server availability for accurate regeneration.

Quick Start

Review the current schema and propose fixes to align with project conventions.

Frequently Asked Questions about graphql

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate GraphQL schema changes to prevent breaking modifications?

To validate GraphQL schema changes safely, enforce scalar usage rules, maintain consistent typing, and check input/output patterns during file modifications to prevent breaking changes.

What is the best way to align GraphQL schemas with codegen requirements?

Aligning GraphQL schemas with codegen requires checking server availability and validating type definitions to ensure accurate regeneration of typed queries and mutations.

How does scalar validation work for GraphQL type systems?

Scalar validation ensures correct usage of custom scalars like NonEmptyString and Email, avoiding nullable pitfalls and enforcing consistent typing across schema definitions.

Can I use this to enforce naming conventions for GraphQL queries and mutations?

Yes, it provides naming and structure guidance by following standard GraphQL patterns for queries, mutations, inputs, and payloads to align schema definitions with project conventions.

Why does editing GraphQL schema files cause codegen errors?

Editing GraphQL schema files causes codegen errors when changes ignore scalar rules, input/output patterns, or server availability prerequisites needed for accurate type regeneration.