Why Changelogs Suck and How I Built 6 AI Journalists to Fix Them

GitHub activity is exploding. With the AI craze pushing more repos, more contributors, and more noise than ever, keeping up with what's actually happening in a repository has become nearly impossible. Changelogs are dry. Release notes are incomplete. Notification feeds are a wall of unreadable noise.

I've spent more time than I'd like to admit buried in GitHub issue threads — scrolling through comments to figure out if a bug was reported, if someone found a workaround, if a fix was even on the radar. And I kept thinking: this is only going to get worse. The amount of activity happening inside repositories is going to grow exponentially, and the way we consume that information hasn't evolved at all.

So I built Git Gazette — a tool that reads all the raw activity of a GitHub repo and turns it into a short, personality-driven newspaper. No manual writing. No curation. Just paste a repo URL and get the full picture in two minutes.

But here's the thing — I didn't want to build just another summarizer.

Why Personalities?

Code activity is cold. PRs, commits, issues — it's all deeply impersonal by nature. I wanted to find a way to process all of that from a human perspective, something you'd actually want to read.

So I started thinking about what makes humans fun and unique. Our drama. The stories we build from reading other people's comments. Poetry. Humor. Predictability in character — like knowing exactly what your friend is going to say before they say it. That kind of warmth.

That's how the columnists were born. Each one has a distinct personality, a voice you can expect and relate to. When Patch Wiresec writes, you know what's coming. Same for Flo or Mergington. There's an element of fun, predictability, and friendliness that gives Git Gazette a human touch that a generic AI summary simply can't.

Meet the Team

The first columnist was Rita Conflictson. She covers the drama — the issue threads, the heated discussions, the back-and-forth between contributors. She was born from years of living inside GitHub issue comment sections on public repos, back when that was the only way to find out if a bug had been reported or resolved. Rita reads between the lines so you don't have to.

Flo and Mergington came next, covering pull requests and code changes. They were a combined effort — I actually got some of the inspiration from bouncing ideas with Claude during the design phase. They break down what's being merged and why it matters, in a way that's actually readable.

Max is the natural editor-in-chief. He writes the TL;DR of everything — the one you read when you have 30 seconds and need the big picture.

The latest addition is Patch Wiresec, the security correspondent. He was born from user feedback. Security has become critical, supply chain attacks are a very common attack pattern now, and people needed someone watching that angle. Patch checks CVEs, advisories, and vulnerabilities so you know if you're in danger or if you can sleep easy.

First Reactions

The early reactions were genuinely encouraging. People found it fun — a tool that's actually enjoyable to use while solving a real problem. What surprised me was how many people immediately started trying different repos, testing the output in both Spanish and English. In hindsight, it makes sense given my audience, but it was cool to see that the multilingual angle resonated right away.

Where I think the real unlock is going to be is with public repo maintainers. General developers get value from it, but maintainers — the people drowning in activity across their own projects — they're the ones who might need this the most.

The repositories are where AI is going to live. And as that activity explodes, the way we read and understand it needs to evolve too. Git Gazette is my bet on what that looks like.