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.