backwards-compatibility-checker

Detect breaking changes across APIs and enforce semantic versioning compliance.

3|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/robotijn/ctoc --skill backwards-compatibility-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backwards-compatibility-checker
Source: https://github.com/robotijn/ctoc/tree/main/skills/versioning/backwards-compatibility-checker
Command: npx skills add https://github.com/robotijn/ctoc --skill backwards-compatibility-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of accidentally shipping breaking API changes that violate semantic versioning rules, which can cause downstream consumer outages, broken integrations, and loss of user trust for teams releasing public libraries, APIs, or SDKs.

Core Features & Use Cases

  • Multi-language API scanning: Detects breaking changes across 10+ programming languages (TypeScript, Python, Java, C#, Rust, Go, C/C++) and contract formats (OpenAPI, gRPC, GraphQL).
  • Semver enforcement: Flags missing version bumps for detected breaking changes, and enforces the 2-minor-release deprecation cycle rule for removed symbols.
  • Actionable reporting: Generates human-readable reports with migration guidance, and integrates with CI pipelines to block breaking changes from merging.
  • Use Case: A team preparing to release v2.0.0 of their public Python SDK can use this Skill to catch removed functions, changed type signatures, and altered default values that would break existing consumer code, and confirm the correct major version bump.

Quick Start

Use the backwards-compatibility-checker skill to scan your project's public API against the previous release and flag all breaking changes that require a semantic version bump.

Frequently Asked Questions about backwards-compatibility-checker

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

FAQPage Schema
How do I detect breaking API changes and enforce semantic versioning in my CI pipeline?

Detect breaking API changes by scanning your public API surface across 10+ programming languages and contract formats to flag removed symbols, changed type signatures, and altered default values, blocking incorrect version bumps from merging in CI pipelines.

What is the best way to check for breaking changes in an OpenAPI or gRPC contract?

Checking for breaking changes in OpenAPI or gRPC contracts involves comparing the new schema against the previous release to identify removed endpoints or altered type signatures, generating actionable migration guidance to prevent downstream consumer outages.

Does backwards compatibility checking work for C and C++ ABI layouts?

Backwards compatibility checking works for C and C++ ABI layouts by scanning the compiled binary interface to identify removed symbols and changed type signatures, ensuring ABI compliance and preventing integration failures for downstream consumers.

How do I automate semver compliance checks for a Rust or TypeScript SDK release?

Automate semver compliance checks for Rust or TypeScript SDK releases by integrating language-specific semver checking tools like cargo-semver-checks and api-extractor to validate the public API surface and confirm the correct version bump before publishing.

Can I enforce a deprecation cycle for removed API symbols before a major version bump?

You can enforce a 2-minor-release deprecation cycle for removed API symbols by scanning the public API surface across versions, flagging immediate removals as violations, and ensuring downstream consumers have time to migrate before the major version bump.