Writing release notes sucks. I know this because I've written them badly, avoided them entirely, and watched teammates procrastinate on them until the last possible second. Every release cycle, someone has to context-switch out of deep work to manually parse commits, figure out what actually matters, and write it in a way that makes sense to someone (dev? manager? users?). It's tedious. It kills flow. It shouldn't be this hard.
So I built Proseflow.
The Problem (or: Why I Started This)
Release notes live in this awkward middle ground. Developers need technical accuracy. Users need clarity about what changed and why they should care. Executives want the business impact. Writing one version that satisfies all three? That's basically impossible, so most teams pick one audience and hope for the best.
Meanwhile, the source of truth—your Git history—is already there. Commits exist. PRs exist. The information is right there. We just need to translate it.
What I Built
Proseflow connects to your GitHub repo via OAuth and does three things:
- Pulls commits and PRs from a date range you specify
-
Generates 3 different versions of your changelog using GPT-4o-mini:
- Developer tone: Technical, includes PR links, highlights breaking changes and dependencies
- User tone: Feature-focused, explains benefits, avoids jargon
- Executive tone: Business impact, metrics, strategic wins
- Displays them side-by-side so you can pick what works, remix, or use as a starting point
No manual parsing. No jumping between tools. You hit generate and get three polished changelogs in seconds.
The whole thing is free. No credits needed, no paywalls. Just connect your repo and start generating.
Try It Now
https://proseflow-v1.vercel.app
It takes ~2 minutes to connect via GitHub OAuth and generate your first changelog. Perfect if you've got a release coming up or just want to see how it handles your commit history.
What I'd Love Your Feedback On
- Which tone is most useful for you? Do you actually need all three, or would a subset be better?
- Tag ranges vs. date ranges? Right now you pick a date range. Would it be better to generate changelogs between git tags/releases instead?
- Which integrations matter most? I'm thinking about adding Slack/Notion/Linear exports. What would actually save you time?
- What else is broken about writing release notes? If you've got a process you hate, I want to hear about it.
The Stack (Brief Version)
- Frontend: Next.js + Tailwind
- Backend: Next.js API routes
- AI: GPT-4o-mini via OpenAI API
- Auth: GitHub OAuth
- Hosting: Vercel
Kept it simple so I could ship fast and iterate based on feedback.
This is a working prototype, not a polished product. I expect rough edges. If you find bugs or have ideas, please leave a comment — I'm actively reading.
What's your biggest pain point with release notes? Does this solve it, or am I missing something obvious?
Top comments (0)