skills.rest
apankov1
apankov1COMMUNITY
Explore all skills by this author →
WebsiteGitHub

breaking-change-detector

Detect and classify breaking changes across contracts, schemas, RPC endpoints, and event types.

5|1|Updated Feb 23, 2026
Search Tags:#compatibility#breaking-changes#event-sourcing#api-contracts#schema-evolution#regression-testing#state-serialization
One-click install
npx skills add https://github.com/apankov1/quality-engineering --skill breaking-change-detector-apankov1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: breaking-change-detector
Source: https://github.com/apankov1/quality-engineering/tree/main/skills/breaking-change-detector
Command: npx skills add https://github.com/apankov1/quality-engineering --skill breaking-change-detector-apankov1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects and analyzes breaking changes across contracts, data schemas, RPC endpoints, WebSocket protocols, serialized state, and event types to prevent regressions and client incompatibilities.

Core Features & Use Cases

  • Classifies changes in contracts and schemas as breaking or safe across six categories.
  • Tracks added/removed event types, API field semantics, and serialized state compatibility.
  • Use cases include API versioning reviews, migration planning, and contract audits with deterministic risk scoring.

Quick Start

Run the breaking-change-detector analysis on your API contracts and schemas to detect breaking changes before releasing.

Frequently Asked Questions about breaking-change-detector

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

FAQPage Schema
How do I detect breaking changes in API contracts and data schemas?▼

You can detect breaking changes by analyzing API contracts and data schemas to classify field modifications across six categories, tracking added or removed event types, and evaluating serialized state compatibility to prevent client incompatibilities.

What is a breaking change in serialized state and event sourcing?▼

A breaking change in serialized state and event sourcing occurs when schema evolution alters event types or field semantics, disrupting session integrity and preventing clients from correctly reading defaults during state deserialization.

How do I check RPC endpoints and WebSocket protocols for client compatibility?▼

Check RPC endpoints and WebSocket protocols for client compatibility by applying deterministic risk scoring to versioning reviews, ensuring that field changes and protocol updates preserve session integrity and prevent regressions.

Can I use this breaking change analysis for API versioning and migration planning?▼

Yes, you can use this breaking change analysis for API versioning and migration planning by auditing contracts to assess field changes, serialized state compatibility, and event type updates with deterministic, reproducible risk scoring.

Does breaking change detection support regression testing for schema evolution?▼

Breaking change detection supports regression testing for schema evolution by analyzing serialized state compatibility and event type updates deterministically, ensuring reproducible results when validating client compatibility across versions.

Related Skills

Explore More Software Engineering Skills→
apankov1apankov1
5

zod-contract-testing

Validate Zod schemas at system boundaries for API and WebSocket contracts.

Community
Advanced
paleoterrapaleoterra
2

sqlite-test-validator

Validate SQLite migrations and schemas with sqlite_validator.py CLI commands.

Community
Intermediate
machenjiemachenjie
4

contract-testing

Enforce executable contract evidence across API, schema, event, and integration boundaries.

Community
Advanced
Andreicr1Andreicr1

api-contract-reviewer

Identify and describe breaking API changes from diffs across endpoints and request/response shapes.

Community
Advanced