breaking-change-detector

Detect breaking API, schema, and interface changes in code.

Updated Jan 5, 2026

Search Tags:#versioning #risk assessment #code safety #change detection #API integrity

Ready to run

npx skills add https://github.com/Marcus-Mok-GH/Claude-code-conductor --skill breaking-change-detector-marcus-mok-gh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: breaking-change-detector
Source: https://github.com/Marcus-Mok-GH/Claude-code-conductor/tree/main/.claude/skills/breaking-change-detector
Command: npx skills add https://github.com/Marcus-Mok-GH/Claude-code-conductor --skill breaking-change-detector-marcus-mok-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill detects and prevents breaking API, schema, and interface changes before they reach production, ensuring API integrity and maintaining client trust.

Core Features & Use Cases

Change Detection: Automatically detects breaking changes in API routes, database schemas, and public interfaces.
Risk Assessment: Analyzes the impact of changes and suggests migration paths for breaking changes.
Validation: Validates changes against the project's API versioning strategy.
Use Case: For a project with a complex API, this Skill can prevent accidental removal of endpoints or modification of public interfaces, which could break existing integrations.

Quick Start

Use the breaking-change-detector skill to analyze changes in your project codebase.

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 routes and database schemas before deployment?▼

To detect breaking changes in API routes and database schemas, you can use automated change detection to analyze codebase modifications and validate them against your project's versioning strategy before deployment.

What is API integrity and how does change detection maintain client trust?▼

API integrity ensures that public interfaces and endpoints remain stable and compatible. Change detection maintains client trust by automatically identifying and preventing accidental modifications to public interfaces that could break existing integrations.

Can I assess the impact of schema modifications and get migration path suggestions?▼

Yes, you can assess the impact of schema modifications through risk assessment, which analyzes codebase changes and suggests specific migration paths for breaking changes to preserve API integrity.

Do I need project documentation to validate code changes against versioning strategy?▼

Yes, you need project documentation and codebase access to validate code changes against versioning strategy, as the analysis requires understanding the existing API structure and project rules to accurately detect interface modifications.

What is the best way to prevent accidental removal of endpoints in a complex API?▼

The best way to prevent accidental removal of endpoints in a complex API is to implement automated change detection that validates modifications against your versioning strategy and flags breaking changes before they reach production.