skill-schema-evolution

Name: skill-schema-evolution
Availability: InStock
Author: meridianhub

Enforces safe protobuf schema evolution with buf breaking-change detection.

10|2|Updated Oct 24, 2025

Search Tags:#validation #protobuf #breaking-changes #schema-evolution #BIAN #buf #ADR-0004

Ready to run

npx skills add https://github.com/meridianhub/meridian --skill skill-schema-evolution

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skill-schema-evolution
Source: https://github.com/meridianhub/meridian/tree/main/.claude/skills/schema-evolution
Command: npx skills add https://github.com/meridianhub/meridian --skill skill-schema-evolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Protobuf schema evolution workflow with buf breaking change detection and BIAN patterns

Core Features & Use Cases

Pattern-based guidance for backward-compatible changes
Support for introducing new event types per BIAN patterns
Local validation workflow using ADR-0004, buf tooling, and pre-commit hooks

Quick Start

Follow ADR-0004 guidelines to validate proto changes locally before committing.

Frequently Asked Questions about skill-schema-evolution

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

FAQPage Schema

How do I detect breaking changes in protobuf schemas before committing?▼

To detect breaking changes in protobuf schemas before committing, use a local validation workflow with buf tooling and pre-commit hooks based on ADR-0004 guidelines. This enforces safe patterns and catches backward compatibility issues locally before commits.

What is backward-compatible protobuf schema evolution?▼

Backward-compatible protobuf schema evolution is the process of modifying proto definitions by applying safe patterns, such as introducing new fields or event types per BIAN patterns, without breaking existing API consumers.

How do I introduce new event types in protobuf while maintaining backward compatibility?▼

To introduce new event types in protobuf while maintaining backward compatibility, follow BIAN patterns for schema evolution alongside ADR-0004 guidance to ensure new events do not disrupt existing API workflows.

Does buf work with ADR-0004 for local proto validation?▼

Yes, buf works with ADR-0004 for local proto validation by providing the tooling and breaking change detection needed to enforce safe schema evolution patterns locally before you commit changes.

What's the best way to manage API schema evolution without breaking existing consumers?▼

The best way to manage API schema evolution without breaking existing consumers is to combine pattern-based backward-compatible guidance with buf breaking change detection and pre-commit validation hooks.

Why should I use pre-commit hooks for protobuf schema validation?▼

You should use pre-commit hooks for protobuf schema validation to enforce ADR-0004 guidelines and catch breaking changes locally before they enter the repository, ensuring safe schema evolution.