update-silver

Align Silver data transformation layers with updated upstream specifications.

5|1|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/RDEWAI/Redefining-DataEngineering-With-AI --skill update-silver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-silver
Source: https://github.com/RDEWAI/Redefining-DataEngineering-With-AI/tree/main/chapter-6/developer-plugin/skills/update-silver
Command: npx skills add https://github.com/RDEWAI/Redefining-DataEngineering-With-AI --skill update-silver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of Silver data transformation layer drift when upstream specifications (logical layer designs, data models, transformation rules, data quality rules) are updated, avoiding broken downstream pipelines and manual full rewrites of unchanged code.

Core Features & Use Cases

  • Controlled Update Modes: Apply only story-authorized changes, diff current code against approved upstream artifacts, or fully regenerate all Silver modules as needed.
  • Automated Versioning & Synchronization: Enforce 3-scenario versioning rules, update contracts, DQ rules, and migration DDL to match upstream changes.
  • Downstream Ripple Protection: Automatically surface required Gold layer updates to prevent breakages from Silver schema or logic changes.
  • Use Case: When a data model adds a new patient race column, the skill updates only the affected Silver transform, its contract, DQ rules, and migration DDL while leaving all other Silver modules untouched.

Quick Start

Use the update-silver skill to align your existing Silver data layer with the latest approved upstream specifications and apply any required downstream ripple updates.

Frequently Asked Questions about update-silver

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

FAQPage Schema
How do I update my Silver data layer when upstream data models or transformation rules change?

To update your Silver data layer after upstream data models or transformation rules change, you can apply controlled updates that diff current code against approved artifacts and synchronize contracts, data quality rules, and migration DDL without rewriting unchanged modules.

What is the best way to prevent Gold layer pipeline breakages caused by Silver layer schema updates?

Preventing Gold layer pipeline breakages from Silver layer schema updates requires surfacing downstream ripple effects automatically, ensuring end-to-end pipeline consistency by identifying required Gold updates before changes are finalized.

How does versioning work when synchronizing Silver data transformations with new upstream specifications?

Versioning for Silver data transformation synchronization works by enforcing 3-scenario versioning rules that update contracts, data quality configurations, and migration DDL to exactly match the approved upstream changes.

Can I selectively apply only authorized changes to a Silver data pipeline without regenerating all modules?

Yes, you can selectively apply authorized changes to a Silver data pipeline using controlled update modes that diff current code against approved upstream artifacts, leaving all unaffected Silver modules completely untouched.

When do I need to regenerate all Silver transformation modules instead of just diffing against upstream artifacts?

You need to fully regenerate all Silver transformation modules instead of diffing when upstream specification changes are extensive enough to require a complete rebuild, which is supported as a controlled update mode alongside story-authorized and diff-based updates.

Does updating the Silver data layer handle catalog migrations for approved logical layer design changes?

Yes, updating the Silver data layer handles catalog migrations by synchronizing contracts and data quality configurations, automatically applying the necessary migration DDL to match the updated upstream specifications.