Schema Evolution Manager
DevelopmentSchema Evolution Manager is an Agent Skill for development published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Manages schema evolution and compatibility across data systems
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/specializations/data-engineering-analytics/skills/schema-evolution-manager/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/schema-evolution-manager, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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