What happens if a critical breaking change is detected?

For critical changes, the skill acts as a safety gate, blocking implementation until a valid migration plan—such as a deprecation timeline or a major version bump—is established.

How does the skill detect a breaking change?

The skill monitors for specific intent patterns in user requests and code modifications, such as 'remove endpoint', 'drop column', or 'change function signature' across API routes and database schemas.

Can I customize the versioning rules?

Yes, the skill automatically reads your project's 'api-strategy.md' file to ensure its recommendations align with your specific versioning and deprecation policies.

Does it support different API versioning strategies?

It supports multiple strategies including URL versioning (/v1/v2), header versioning, and deprecation-only models, providing specific migration steps for each.

Breaking Change Detector

Name: Breaking Change Detector
Author: marcusgoll

bymarcusgoll

•

API Development

Identifies and mitigates breaking API, database, and interface changes before they reach production to maintain system stability.

The Breaking Change Detector acts as an automated safety gate for your development workflow, specifically designed to prevent unintentional regressions in APIs and database schemas. It monitors for modification patterns like endpoint deletions, altered request/response formats, and dropped database columns, providing severity-rated warnings and actionable migration paths. By validating changes against your project's versioning strategy, it ensures that software evolution remains backward-compatible and client trust is preserved through structured deprecation and versioning workflows.

Key Features

01Actionable migration path suggestions including versioning and dual-write strategies

02Validation against project-specific api-strategy.md versioning rules

03Automated detection of API, database, and function signature modifications

04Smart blocking of implementation for critical changes lacking a migration plan

05Severity-based risk assessment ranging from CRITICAL to LOW impact

0618 GitHub stars

Use Cases

01Enforcing strict backward compatibility in large-scale microservice architectures

02Evolving a production API without breaking legacy mobile applications or partner integrations

03Refactoring complex database schemas while avoiding data loss or downtime

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add marcusgoll/spec-flow breaking-change-detector

For use in Claude.ai and ChatGPT

Download Skill