Skip to content

a5c-ai/babysitter / library/specializations/data-engineering-analytics/skills/schema-evolution-manager

Schema Evolution Manager

Verified

Manages schema evolution and compatibility across data systems

FileKindSize
README.mdmarkdown486 B
SKILL.mdskill md2.0 KB
---
name: Schema Evolution Manager
description: Manages schema evolution and compatibility across data systems
version: 1.0.0
category: Data Governance
skillId: SK-DEA-011
allowed-tools:
  - Read
  - Write
  - Edit
  - Glob
  - Grep
  - Bash
graph:
  domains: [domain:data-engineering]
  specializations: [specialization:data-engineering-analytics]
  skillAreas: [skill-area:schema-evolution, skill-area:data-governance]
  roles: [role:data-engineer, role:analytics-engineer]
  workflows: [workflow:data-pipeline-deployment]
  topics: [topic:data-mesh]
---

# 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

```json
{
  "currentSchema": "object",
  "proposedSchema": "object",
  "schemaFormat": "avro|protobuf|jsonschema|ddl",
  "compatibilityMode": "backward|forward|full|none"
}
```

## Output Schema

```json
{
  "compatible": "boolean",
  "breakingChanges": ["object"],
  "migrationScript": "string",
  "recommendations": ["string"],
  "versionInfo": "object"
}
```

## Target Processes

- Streaming Pipeline
- ETL/ELT Pipeline
- Data Catalog
- Pipeline Migration

## Usage Guidelines

1. Provide current and proposed schema definitions
2. Specify schema format for proper parsing
3. Define compatibility mode based on system requirements
4. 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
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall