anti-compat

Apply controlled breaking changes to software artifacts and generate migration notes.

6|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/archibate/archibate-skills --skill anti-compat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anti-compat
Source: https://github.com/archibate/archibate-skills/tree/main/old-skills/redundant-skills/anti-compat
Command: npx skills add https://github.com/archibate/archibate-skills --skill anti-compat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Introduces controlled breaking changes to surface compatibility regressions and validate upgrade and migration workflows, helping teams discover integration failures before production releases.

Core Features & Use Cases

  • Simulated Breaking Changes: Create reproducible change manifests that emulate incompatible API or library updates in a safe environment.
  • Migration Guidance: Produce deprecation notes and migration checklists to support downstream consumers in upgrading.
  • Use Case: Run compatibility simulations in CI to ensure a major version bump includes clear migration steps and does not silently break dependent services.

Quick Start

Use the anti-compat skill to simulate a breaking API change for my service and generate a migration checklist.

Frequently Asked Questions about anti-compat

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

FAQPage Schema
How do I simulate breaking API changes to test compatibility in my CI pipeline?

To simulate breaking API changes, apply controlled incompatibilities to your software artifacts within staging workflows. This surfaces compatibility regressions and validates migration workflows before production releases.

What is a breaking change simulation and when do I need it for versioning?

A breaking change simulation introduces controlled incompatibilities to surface integration failures. You need it during major version bumps and migration planning to ensure dependent services do not silently break.

How do I generate a migration checklist for an upcoming major version bump?

Generate a migration checklist by running compatibility simulations against your service. This produces explicit deprecation notes and reproducible change manifests to support downstream consumers upgrading.

Can I run compatibility audits in testing workflows without executing destructive system operations?

Yes, you can run compatibility audits in testing workflows without destructive operations. The process safely produces deprecation warnings and change manifests to validate upgrade paths in staging environments.

What's the best way to surface deprecation warnings for downstream consumers?

The best way to surface deprecation warnings is to simulate library updates in a safe environment. This generates explicit migration notes and reproducible change manifests for consumers.

Why does my major version bump silently break dependent services?

A major version bump silently breaks dependent services when compatibility regressions go unnoticed. Running controlled breaking change simulations in CI surfaces these integration failures before production release.