Babysitter Schema Evolution Manager
Manages schema evolution and compatibility across data systems
install
source · Clone the upstream repo
git clone https://github.com/a5c-ai/babysitter
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/specializations/data-engineering-analytics/skills/schema-evolution-manager" ~/.claude/skills/a5c-ai-babysitter-schema-evolution-manager && rm -rf "$T"
manifest:
library/specializations/data-engineering-analytics/skills/schema-evolution-manager/SKILL.mdsource content
Schema Evolution Manager
Overview
Manages schema evolution and compatibility across data systems. This skill ensures safe schema changes that maintain backward and forward compatibility.
Capabilities
- Schema compatibility checking (Avro, Protobuf, JSON Schema)
- Breaking change detection
- Migration script generation
- Version management
- Schema registry operations
- Backward/forward compatibility validation
- Schema documentation generation
- Cross-system schema synchronization
Input Schema
{ "currentSchema": "object", "proposedSchema": "object", "schemaFormat": "avro|protobuf|jsonschema|ddl", "compatibilityMode": "backward|forward|full|none" }
Output Schema
{ "compatible": "boolean", "breakingChanges": ["object"], "migrationScript": "string", "recommendations": ["string"], "versionInfo": "object" }
Target Processes
- Streaming Pipeline
- ETL/ELT Pipeline
- Data Catalog
- Pipeline Migration
Usage Guidelines
- Provide current and proposed schema definitions
- Specify schema format for proper parsing
- Define compatibility mode based on system requirements
- Review breaking changes before proceeding with migration
Best Practices
- Always test schema changes in non-production first
- Use schema registry for centralized schema management
- Document schema versions and changes
- Plan migration strategies for breaking changes
- Coordinate schema changes across dependent systems