How does it handle breaking changes that aren't actually used by clients?

It supports usage-based diffing via the 'considerUsage' rule, which checks schema changes against real-world operations to ignore breaking changes that don't impact actual application usage.

What is the difference between a Breaking and a Dangerous change?

Breaking changes (like removing a field) will definitely fail existing queries, while Dangerous changes (like adding a value to an Enum) might break specific client implementations or switch-case logic.

Is Apollo Federation supported?

Yes, the skill includes specialized support for Apollo Federation, allowing you to compare federated subgraphs to ensure compatibility within microservices environments.

Can this skill compare local schemas with remote production endpoints?

Yes, it can perform URL-based comparisons between local files and live GraphQL endpoints or even compare two different remote URLs directly.

Can I use this in my CI/CD pipeline?

Absolutely. The skill provides patterns for GitHub Actions and GitLab CI to automate schema validation and report breaking changes during the code review process.

GraphQL Schema Inspector & Diff

Name: GraphQL Schema Inspector & Diff
Author: TheBushidoCollective

byTheBushidoCollective

•

API開発

Detects breaking changes and validates GraphQL schema migrations across files, git branches, and remote endpoints.

This skill empowers Claude to perform sophisticated GraphQL schema analysis using the GraphQL Inspector CLI. It enables automated detection of breaking, dangerous, and non-breaking changes between different schema versions, whether stored locally, in git repositories, or hosted on remote servers. By integrating with CI/CD workflows and supporting usage-based diffing, it helps developers prevent API regressions, manage deprecation cycles, and ensure the smooth evolution of GraphQL APIs without disrupting client applications.

主な機能

01Usage-based diffing to ignore breaking changes that don't affect real operations.

0295 GitHub stars

03Comprehensive schema comparison across local files, git branches, and live URLs.

04Apollo Federation support for comparing subgraphs in microservices architectures.

05Categorization of changes into Breaking, Dangerous, and Non-breaking impacts.

06Customizable rules and CI/CD integration for automated pull request validation.

ユースケース

01Validating schema changes in pull requests to prevent breaking client applications.

02Planning safe migrations by identifying fields that need deprecation before removal.

03Auditing the evolution of a GraphQL API by comparing production vs. development schemas.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add thebushidocollective/han graphql-inspector-diff

For use in Claude.ai and ChatGPT

Download Skill