schema-check

Detects schema drift between canonical sources and local mirrors.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-kit --skill schema-check-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schema-check
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/schema-check
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill schema-check-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconcile this project's local schema mirror against an externally-owned canonical schema (iOS Realm models, backend protobufs, OpenAPI specs, GraphQL schemas, partner API docs, etc.). Detects drift between what the canonical source says and what this codebase mirrors. Triggered when the user says — e.g. "/schema-check", "iOS just shipped a new field", "check our models against the API", "is our schema still in sync".

Per CLAUDE.md: honest reporting. If a field is missing, say so. If the source-of-truth wasn't reachable, say so plainly — don't fabricate parity.

Process overview

  • Identify the canonical source first. The canonical source is provided by the user or located via CLAUDE.md cues.
  • Identify the local mirrors. Locate where the project mirrors live (models, types, validators, etc.).
  • Diff field-by-field. Compare canonical vs mirror for missing/extra/renamed/type/default discrepancies and any path changes, without applying fixes.

Core Features & Use Cases

  • Surface field-level drift between canonical schemas and local mirrors (names, types, optionality, defaults).
  • Respect the schema-discipline rule: mirror must reflect the canonical source verbatim, including any upstream typos.
  • Produce a structured report highlighting breaking vs latent drift, plus cosmetic notes, to guide remediation tasks (/task).

Quick Start

Paste or point to the canonical source and run a drift check against the local mirror to generate a report.

Frequently Asked Questions about schema-check

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

FAQPage Schema
How do I detect schema drift between an OpenAPI spec and my local models?

Detect schema drift by diffing the canonical OpenAPI source against your local mirror field-by-field, surfacing missing, extra, renamed, or type discrepancies in a structured report without modifying any source files.

What is a canonical schema drift check?

A canonical schema drift check reconciles an externally-owned schema, such as GraphQL or protobuf definitions, against local mirrors to identify parity gaps and breaking changes without applying remediation.

How do I check if my protobuf models are still in sync with the backend?

Check protobuf model sync by comparing the backend canonical protobufs against your local repository mirrors to surface field-level drift, including optionality and default value discrepancies, in a generated report.

Does the schema drift report include remediation steps or fixes?

The schema drift report does not include remediation steps or apply fixes; it strictly surfaces breaking versus latent drift and cosmetic notes to guide separate remediation tasks while enforcing verbatim adherence to the canonical source.

Can I use this to compare iOS Realm models against an upstream API schema?

Yes, you can compare iOS Realm models against an upstream API schema by locating the canonical source and local mirrors, then diffing them to report any missing fields or type changes without modifying the source.

What happens if the canonical schema source is not reachable during a drift check?

If the canonical schema source is not reachable during a drift check, the report will plainly state that the source-of-truth was inaccessible and will not fabricate parity, ensuring honest reporting of the actual sync status.