Skip to content
Back to skills

Pipelines Batch Schema Evolution Contracts

ASecurity

Schema contracts, compatibility modes, and deprecation flows across pipeline boundaries.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 29, 2026
ai-agentsbashgit

Works with

  • cli

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add aniruddhaadak80/skills --skill pipelines-batch-schema-evolution-contracts --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pipelines Batch Schema Evolution Contracts?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pipelines Batch Schema Evolution Contracts
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aniruddhaadak80-pipelines-batch-schema-evolution-contracts/badge)](https://www.skillsdirectory.com/skills/aniruddhaadak80-pipelines-batch-schema-evolution-contracts)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pipelines-batch-schema-evolution-contracts
description: "Schema contracts, compatibility modes, and deprecation flows across pipeline boundaries."
---
# Evolve schemas without breaking consumers

> Schema contracts, compatibility modes, and deprecation flows across pipeline boundaries.

**Track:** 🛢️ Data Engineering · **Domain:** Batch Pipelines · **Level:** advanced · **~40 min**

**Who this is for:** Data Engineers, Analytics Engineers, Platform Data Teams

## When to Use This Skill

Schema contracts, compatibility modes, and deprecation flows across pipeline boundaries.
Use it whenever a matching task appears in conversation — the agent loads these instructions on demand.

## Steps

1. Publish schema contracts per dataset with owner + compatibility mode (backward default)
2. CI-validate producer changes against registered contracts
3. Add columns nullable-first; never repurpose existing fields silently
4. Rename via add-new → dual-write → migrate → drop-old, with telemetry at each step
5. Notify consumer list (derived from query logs) before breaking changes
6. Archive old schema versions; make lineage queryable

## Common Pitfalls

- "Temporary" column reuse changing meaning mid-history
- Producers shipping struct changes on Friday evenings

## Commands

**Install with skills CLI**
```bash
npx skills add aniruddhaadak80/skills --skill pipelines-batch-schema-evolution-contracts
```

**Install globally**
```bash
npx skills add aniruddhaadak80/skills --skill pipelines-batch-schema-evolution-contracts -g
```

---

Part of [aniruddhaadak80/skills](https://github.com/aniruddhaadak80/skills) · Browse all at https://skills.sh/aniruddhaadak80/skills

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…