Claude Wrote Our Release Notes From the Commit Log and Nobody Complained

Point it at the diffs and tell it who's reading. The rest is editing.

Release notes usually rot in a doc nobody opens. I pointed Claude at the merged commits and asked for a one-paragraph summary per feature.

It grouped the changes by user impact instead of by file, which is the order people actually read.

I made it leave out internal refactors unless they changed behavior, because readers don't care about our plumbing.

The draft still over-explained one fix, so I cut it to two lines. The model padds when you let it.

Shipped in twenty minutes. The only complaint was that it was too short, which is a good problem.

Más guías

The AI draft is the starting point, not the send button. Here is the three-pass routine that keeps it human.

A research paper I'd been avoiding became a 25-minute walk. The workflow is dumb, and that's why it worked.

Not zero-inbox. A loop that decides what is real so I only touch email twice a day.