Skill: api/compatibility-check
Purpose
Determine whether an API change is:
- backward-compatible
- conditionally compatible
- breaking
And make that status explicit before shipping.
Inputs
- Old contract
- New contract
- Known consumers (if available)
Outputs
- Compatibility assessment:
- compatible / breaking / unsafe
- Explicit list of breaking changes (if any)
- Recommendation:
- proceed
- version
- block
Non-goals
- Modifying contracts
- Updating clients
- Implementing migrations
Workflow
- Compare old vs new contract shapes.
- Identify removed or behaviorally changed fields.
- Assess consumer impact.
- Emit a clear compatibility verdict.
Checks
- All removals and type changes enumerated
- Verdict is explicit and justified
Failure modes
- Missing baseline contract → block and request one.
- Ambiguous change → recommend
meta/spec-sculptor.
Telemetry
Log:
- skill:
api/compatibility-check - verdict
- affected_consumers
- outcome