API Changelog Generator
Compare two OpenAPI documents and explain contract changes to API consumers.
Get a changelog with path-level evidence and breaking-change candidates.
Free · 2 KB · SKILL.md, instructions and example files. Provide both specifications and their OpenAPI version; a parser is needed for local schema validation.
A worked example
A small example to try before using your own data.
Input
{
"before": {
"GET /items": "optional query limit; response id,title"
},
"after": {
"GET /items": "required query limit; response id,title,tag"
}
}Expected result
Breaking candidate: GET /items now requires limit; existing callers without it may fail. Response addition: tag is added; compatibility depends on whether consumers reject unknown response fields. Confirm against actual schemas and client behavior.
What to check: Identify the required-input change without automatically treating an additive response field as universally safe or breaking.
Limits: A specification diff does not prove server behavior. Test representative clients before claiming compatibility.
Worked example included. Model-specific performance and vendor compatibility have not been benchmarked.
🧠 Why it works
Identify the required-input change without automatically treating an additive response field as universally safe or breaking.
⚙️ How it works
- Validate both documents and resolve local references before comparing operations.
- Match operations by path and method, then compare parameters, request bodies, responses and security requirements.
- Treat removal, new required inputs and narrower accepted values as possible breaking changes; distinguish response additions from request restrictions.
- Keep implementation behavior separate from the documented contract and flag unresolved references.
- Return consumer actions and exact before/after locations; do not label every textual edit as a breaking change.
Description
Get a changelog with path-level evidence and breaking-change candidates.
Provide both specifications and their OpenAPI version; a parser is needed for local schema validation.
Limits: A specification diff does not prove server behavior. Test representative clients before claiming compatibility.
Recommended Use
Sign in to suggestTools and workflow packs this skill pairs well with. Forge picks are auto-generated from category + capability signals; Community picks are added by people who've used the pairing.
No matches yet. Be the first to suggest a pairing, or the Forge will populate suggestions as signals align.
Report compatibility
Tell the community which tool you used this skill with, and whether it worked.
Suggest a pairing
Recommend a tool or workflow pack that this skill works well with. Up to 5 recommendations per day.