Weekly Changelog Agent with Hermes
Fifty-two runs a year, each reading a week of merges and deciding what a non-engineer needs to know. The reading is cheap; the judgement is collapsing six related pull requests into one line and pitching it at support rather than at the author. Hermes brings general reasoning to that on an open model foundation.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Friday 15:00 changelog tick
It is Friday 15:00 in Berlin. Twenty three pull requests merged across the api and dashboard repos this week, including one that renames a field in the settlement webhook payload and one that removes a reporting endpoint two customers still call. The audience is support and the twelve merchants on the beta.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect GitHub
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Repo context
Which repositories to cover, who reads this changelog (customers, support, the whole company), and who to tag when a repository goes silent or a call fails.
Changelog style
How your changelog should read: how technical to get, whether dependency bumps and internal refactors make the cut, and how long it can run before people skim.
Runs on Hermes
Preselected for this page — connect your Hermes account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Hermes for this agent
Audience pitch is judgement
The same merge is one sentence for support and a different one for beta merchants. Choosing which is reasoning rather than retrieval.
Collapsing related merges
A stack of five pull requests should read as one shipped thing, named by the largest. That grouping is where a changelog stops being a list.
Before you fork
Will it invent a benefit that was never claimed?
That is the specific risk with a fluent model, and the template answers it by allowing only what the pull request text says. Use Busy Shipping Week, where a renamed settlement webhook field and a removed reporting endpoint both belong in BREAKING with the author's own migration wording. Any line about improved reliability that no author wrote is your signal to tighten the style variable.
Run it with a different agent
Put Weekly Changelog Agent to work on Hermes
Free to start. Guided setup, a test run against staged conversations, and it's live.