ChatGPT API Changelog Skill for Breaking Changes and Migration Notes
Convert API differences into a Markdown release entry with a compatibility classification and concrete client migration notes.
中文Install in ChatGPT
Use a ChatGPT workspace with skill creation enabled. Supply JSON showing changes to endpoints or fields, optionally with the version and release date.
- In a ChatGPT workspace with skill creation enabled, open Plugins → Skills → Create → Create with editor.
- Create a skill in the editor and adapt the text-only `api-changelog-summarizer` workflow from the pinned GitHub source into its instructions.
- Save the skill, then type @ in a new chat to select it and try the example.
Example task
Create an API changelog from this fictional library catalog diff.
{"version":"2.0","endpoint":"GET /shelves","removedResponseField":"sectionName","addedResponseField":"shelfLabel"}What to check
Classify removal of `sectionName` as a breaking change. Identify `GET /shelves` as the affected endpoint and mention `shelfLabel` in the migration notes for client field mapping.
Original SKILL.md on GitHub · Updated
Frequently asked question
Can the ChatGPT API changelog assume the old and new fields mean the same thing?
Mark equivalence for review when the supplied diff only shows fields being added and removed. Describe the observed breaking changes and the items clients should confirm.