Landing copy from a feature list
writingTurns what the product does into what it removes from the reader's day.
Changelog from raw commit history
Groups commits into user-facing changes, without inventing anything that is not in the log.
When to use it
The day before a release, with forty commits and no writing time.
The prompt
Copy into your assistant
Write a user-facing changelog from the commit log below.
Rules:
- Group under: Added, Changed, Fixed, Removed.
- One line per user-visible change. Omit internal refactors, dependency bumps, and test changes.
- Do not invent impact. If a commit says "fix pagination", write "pagination on the results page", not "dramatically faster search".
- If a commit's user impact is unclear, list it under "Internal" rather than guessing.
- Keep the whole thing under 250 words.
Commits:
<log>What to change
Feed it squashed merge commits if you have them — raw WIP history produces a changelog of the author's afternoon rather than the release.
Why it works
The 'unclear impact goes under Internal' rule is what stops the model from writing marketing. Changelogs lose trust the first time they claim something the release did not do.
More writing prompts
- Landing copy from a feature listTurns what the product does into what it removes from the reader's day.
- Incident postmortem from a raw timelineTurns logs and a chat transcript into a blameless postmortem with contributing factors, not a culprit.
- Meeting transcript to decisions and ownersExtracts what was decided, what was merely discussed, and who owes what by when.
Going deeper
- Prompts that survive contact with realityUsing agents · Level 2
- Writing a skill that changes behaviorSkills and prompts · Level 2
- The last hour before launchRunning agents in production · Level 3