Check merged PRs for docs drift each week

Use a weekly agent run to spot merged code changes that should have updated documentation.

Done with Hermes Agent· Intermediate

What they did
A Hermes cron job was scheduled for Monday mornings. Each run used the gh CLI to pull the latest 30 merged PRs from the hermes-agent repo, narrowed that set to the past 7 days, and looked for edits to tool definitions, CLI commands, config settings, or environment variables. For any matching PR, it checked whether the related docs page changed in the same merge, then sent a Telegram summary.
How it went
The output is a gap report: PRs where code changed but the docs did not. If nothing is out of sync, Hermes returns [SILENT] and no message is sent.
Tips
The setup is tied to this repo’s file layout, so update the paths before reusing it elsewhere. If your team merges more than 30 PRs in a week, increase the lookup limit or some changes may be missed.

Try it yourself with Hermes Agent

Every [Monday at 9am], review the PRs merged into [repo name] during the last 7 days. Use [gh CLI or your preferred GitHub tool] to find changes to [tool schemas, CLI commands, config options, environment variables], then check whether the matching pages in [docs path] were updated in the same PR. Send a brief report with the PR links and the likely docs gaps. Do not edit, open, or submit any docs; if you are about to make a change or send anything, pause and ask me to approve first. If nothing needs attention, return [SILENT].

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.