ChangelogPilot is live

We've spent the last few months building a tool to fix a problem we kept running into ourselves: PRs get merged every week, customers don't hear about it, and the changelog page stays exactly where it was three weeks ago.

Today ChangelogPilot is live. Here's what it does and why we built it the way we did.

What it does

Connect a GitHub repo. ChangelogPilot reads your merged PRs and drafts a changelog entry in plain English — the way you'd explain the change to a customer, not the way the commit message reads. You review the draft, edit it if you like, and publish it to a hosted page. When a PR merges, the draft is usually waiting for you in under a minute.

That's the whole workflow: connect, review, publish. No blank editor, no category picker to set up first, no separate writing step.

Why we built it this way

Most existing changelog tools assume writing the entry is the job, and try to make the writing more pleasant — a nicer editor, a template, an AI pass to tidy up whatever you typed. That's a reasonable thing to build. It's just not the problem most small teams actually have.

The problem we kept seeing — in our own team and in the teams we talked to — wasn't a clunky editor. It was that nobody had the spare twenty minutes on a Friday to sit down and write the thing at all. The changelog wasn't badly written. It was unwritten.

So ChangelogPilot doesn't hand you a better blank page. It removes the blank page. The merged PR is the input, the draft is the output, and your job is to approve it.

Where we are

We're early stage, working through real repos with real, sometimes messy PR histories rather than clean demo data.

If you're a small SaaS or dev-tool team on GitHub who's been meaning to fix your changelog for longer than you'd like to admit, this is built for you. It's free to start — sign in, connect a repo, and publish your first changelog.

What's next

More repos, more PR histories, more edge cases. We'll keep this blog honest about what's working and what isn't.