Release Notes Generator Skill for Codex
Turn merged changes, tickets, and changelog fragments into release notes for customers or internal teams. Preserve migration requirements, rollout restrictions, and known issues.
中文Install in Codex
Use a Codex environment that can discover project skills. The example can be tested in a local project.
- In a temporary directory, run git clone https://github.com/ClarentCinematics/Codex-Skills-for-Enterprise.git. Enter the clone, run git checkout --detach 3598e7788282b6548430aadfcbfcfd7181ebb02a, and review the pinned SKILL.md.
- Copy the entire skills/release-notes-generator folder to .agents/skills/release-notes-generator in your own project, keeping its scripts, templates, and references together.
- Open Codex in that project. Choose the skill with /skills or mention $release-notes-generator, then run the example below. Restart Codex if the list does not refresh.
Example task
Provide three fictional changes: a search-filter fix, CSV export for a pilot group, and removal of the export_date field. Request a customer version and an internal version with the release date left open.What to check
The customer notes explain the fix and migration requirement without promising CSV export for everyone. The internal version records the pilot condition and leaves the unknown date open.
Original SKILL.md on GitHub · Updated
Frequently asked question
Should release notes copy every commit message?
Group changes by their effect on readers. Multiple commits for one feature can become one entry while preserving compatibility, migration, and rollout details.