Changelog and Release Notes Audit
Check that notes tell users what changed and what to do.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Audit release notes. Notes for the last three releases: [RELEASE_NOTES]. Users and how they read them: [USERS]. Check clarity from the user's point of view, breaking changes marked with actions, links to details, version and date, grouping, and tone. Identify internal jargon and missing items found from the commit list: [COMMIT_LIST]. Return a table of problems and a rewrite of one release's notes. Add a worked rewrite: Fixed bug in module X becomes You can now export reports as CSV from the Reports page; before, the export button failed for files over 10 MB. Action: none required. Add a standard template with sections New, Improved, Fixed, Breaking changes and Action required. Compare the notes with the commit list and list user-visible changes that were left out. Add a short template with sections New, Improved, Fixed, Breaking changes and Action required, and a rule that every item is written from the user's point of view and checked by someone who did not write the code.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.