Right before a deployment, someone asks when the release notes will be ready. Twenty PRs have already been merged, each titled something like 'fix: button style' or 'refactor: auth module.' Turning those into readable sentences for users means opening each PR one by one. Claude Code handles that step for you.
The Short Answer
In the Claude Code terminal, paste your list of merged PR titles and add a request like: 'Turn this list into release notes written for users. Split into three sections: new features, improvements, and bug fixes.' The result drops the technical jargon and focuses on changes users actually experience.
Why This Matters Now
Many teams publish release notes that arestill written in developer language. Titles like 'auth module refactor' are clear to engineers but meaningless to external stakeholders or customers. Writing good notes from scratch takes time you do not have at deployment. Claude Code takes the raw PR list as input and returns a polished, audience-appropriate document. The benefit grows with PR volume — ten or more PRs from multiple contributors can be unified into a single consistent tone in one pass.
Step-by-Step Instructions
- Run
git log --merges --oneline --since='2 weeks ago' --pretty=format:'%s'to pull merged PR titles from your terminal. - Copy the output and paste it into Claude Code.
- Follow with this prompt: 'Write user-centered release notes from the list above. Use three sections — new features, improvements, and fixes — and write each item as one sentence describing what the user experiences.'
- Refine the output by adding context: if the audience is internal, add 'technical terms are fine'; if external customers, add 'avoid jargon and use plain language.'
- Close the session by asking: 'Add the version number and release date to the top.'
Real-World Example
Assume your PR list looks like this:
- fix: resolve null pointer on login page
- feat: add dark mode toggle
- perf: reduce image load time by lazy loading
- fix: incorrect total on checkout summary
Asking Claude Code to 'convert this PR list into release notes for a B2C mobile app, written from the user's perspective' produces output in this direction:
New feature: A dark mode toggle is now available in app settings.
Improvement: Images load faster, especially when scrolling through the feed.
Fixes: Resolved a login error that appeared on certain devices. Fixed an incorrect total shown on the checkout summary screen.
Changing the audience label to 'B2B SaaS changelog for enterprise clients' shifts the tone and emphasis without changing the underlying PR data.
Common Mistakes
Pasting only PR titles with no context: If titles are vague, Claude Code relies on guesswork. Include the PR body summary or linked issue number for more accurate output.
Skipping audience specification: A bare 'write release notes' request produces safe but generic copy. Specifying 'for external customers,' 'for the internal QA team,' or 'for a technical changelog' raises the quality significantly.
Publishing without review: Claude Code can misread a PR's scope or phrase a change inaccurately. Cross-check each output item against the original PR before publishing.
Checklist
- Did you include PR body summaries or issue references where available
- Did you specify the intended audience in your prompt
- Are all three sections — new features, improvements, fixes — present and filled
- Have technical terms been adjusted to match the audience's level
- Is the version number and release date included at the top
- Have you verified each item against its source PR for accuracy
FAQ
Q. What if there are too many PRs to paste at once?
For more than fifty PRs, split them into two batches and process each separately. Then ask Claude Code to 'merge these two results into a single release note.' Alternatively, sort by category first and summarize each category in a separate pass.
Q. Our PR titles are in English but we need Korean release notes. Does that work?
Yes. Append 'write the output in Korean' to your prompt. Claude Code will translate English PR titles into natural Korean user-facing sentences. You can also specify whether brand names or product terms should stay in English.
Q. Is there a way to save the format so I do not have to explain it every time?
Create a RELEASE_NOTE_TEMPLATE.md file at the project root and tell Claude Code to 'follow the format in this file.' If you add release note formatting rules to your CLAUDE.md, Claude Code will reference them automatically in every new session.
Wrap-Up
Release notes are the last step of a deployment but the first moment your product speaks directly to users. If pasting a PR list is all it takes to get a clean, audience-appropriate document back, you can put that saved time to better use. Try it on your next deployment.
🐦 Faster updates on X: @baegseungh7061
📚 More in this series: Code Intro
💌 Subscribe: Follow on X or grab the RSS
댓글
댓글 쓰기