backwards-compatibility-checker

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.