schema-sync

Audit schema enums, Python constants, overlays, and registry definitions for cross-layer mismatches.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SameerG7/synthesis-hackathon-aibom --skill schema-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schema-sync
Source: https://github.com/SameerG7/synthesis-hackathon-aibom/tree/main/.claude/skills/schema-sync
Command: npx skills add https://github.com/SameerG7/synthesis-hackathon-aibom --skill schema-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent schemas, enums, overlays, and registry mappings across bom/schema, verifier/api, and dashboard layers can cause runtime errors and silent data quality gaps. This Skill audits cross-layer definitions to detect drift and enforce alignment before deployment. It provides a clear remediation path when mismatches are found.

Core Features & Use Cases

  • Discover and compare schema enums across bom/schema files and Python constants.
  • Verify that overlays’ locator kinds and platform keys align with the schema and registry.
  • Validate completeness scorer mappings and API serialization alignment to prevent feature drift.
  • Use Case: After changing a field enum or locator kind, run schema-sync to ensure all layers reflect the update.

Quick Start

Run the audit workflow to compare schema enums, registry mappings, and overlays across all layers.

Frequently Asked Questions about schema-sync

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

FAQPage Schema
How do I check schema consistency across multiple application layers?

To check schema consistency, run an audit workflow that compares schema enums, Python constants, and overlays across bom/schema, verifier/api, and dashboard layers to detect drift and enforce end-to-end alignment.

Why does my API serialization drift after updating schema enums?

API serialization drifts when schema enums, Python constants, and registry mappings are not updated together. Validating completeness scorer mappings and API serialization alignment prevents this feature drift.

What is the best way to validate overlay locator kinds against a registry?

The best way to validate overlays is to run an audit that verifies overlay locator kinds and platform keys align with the schema and registry definitions, flagging deviations for fast remediation.

Can I detect mismatches between Python constants and schema enums automatically?

Yes, you can detect mismatches automatically by running a cross-layer audit that discovers and compares schema enums in bom/schema files against Python constants, flagging any deviations.

When do I need to run a cross-layer schema alignment audit?

You need to run a schema alignment audit after changing a field enum or locator kind to ensure all layers reflect the update, preventing runtime errors and silent data quality gaps before deployment.