Api Contract Compatibility Review
Use when an API, schema, payload, event, or contract change must be checked for backward compatibility, client impact, versioning risk, and migration safety.
Install
$ agentstack add skill-motao123-dev-workflow-kit-api-contract-compatibility-review ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-motao123-dev-workflow-kit-api-contract-compatibility-review) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
API Contract Compatibility Review
Use this skill when the main risk is breaking consumers through interface changes.
Trigger Conditions
Use this skill when:
- request or response shapes are changing
- schema, event, or payload contracts may break old clients or downstream services
- the user asks whether a change is backward compatible
- versioning, migration, or deprecation strategy needs review
- integration risk matters more than internal implementation details
Do not use this skill for generic refactor planning or dependency/license review.
Workflow
- Identify the contract under change.
- Compare current and proposed behavior or shapes.
- Check backward and forward compatibility risks.
- Identify affected consumers, migration needs, and deprecation concerns.
- Recommend versioning or rollout safeguards.
- Suggest verification and communication steps.
Output
For non-trivial work, provide:
- contract surface reviewed
- compatibility risks
- likely breaking changes
- migration or versioning guidance
- verification focus
- recommended next action
Coordination
After contract review:
- use
change-impact-analysisif the consumer surface is still unclear - use
release-rollout-strategywhen compatibility risk changes rollout shape - use
docs-writerwhen migration guidance or deprecation notes should be published
Invocation Examples
- "Use api-contract-compatibility-review to check whether this endpoint change breaks old clients."
- "Use api-contract-compatibility-review on this event schema update before release."
- "Use api-contract-compatibility-review and tell me whether we need versioning or migration guidance."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: motao123
- Source: motao123/dev-workflow-kit
- License: MIT
- Homepage: https://motao123.github.io/dev-workflow-kit/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.