Changelog Entry Skill for ChatGPT: Write a User-Facing Release.md Note
Draft a concise release note from confirmed change facts. Describe previous behavior, what changed for users, and any action they should take.
中文Install in ChatGPT
Use an eligible ChatGPT workspace with permission to create skills and, for uploads, upload permission. The installation path for this text-only adaptation was checked against OpenAI documentation. Workspace runtime verification is pending.
- Download .claude/skills/writing-a-changelog-entry/SKILL.md from the pinned GitHub source. Keep the name, description, and instructions for writing-a-changelog-entry together as a standalone text skill.
- In a ChatGPT workspace with skills and uploads enabled, open Plugins, Skills, Create, and Upload from your computer. Choose a skill package format accepted by the file picker. You can also choose Create with editor and enter the original name, description, and instructions.
- After the scan completes, check that writing-a-changelog-entry appears in Installed. Type @ in a new chat, select the skill, and use the fictional example on this page to check the output.
Example task
A fictional importer used to treat CSV headings padded with spaces as unknown fields. It now trims the headings. Write a RELEASE.md entry for users. No version was supplied.What to check
Describe the import behavior users will notice and whether existing CSV files still work. Leave the version to the release process and omit internal function names.
Original SKILL.md on GitHub · Updated
Frequently asked question
Does an internal function rename need its own release note?
Check the project's release convention. User-facing copy should describe the practical change. Engineering notes can document internal refactors.