agentusecasesAll 965 use cases
Software & DevOps

Flag documentation drift from merged PRs weekly

A weekly Hermes cron job checks merged PRs for changes to tool schemas, CLI commands, config options or env variables to flag docs needing updates.

Done withHermes Agent

What they did
A Hermes cron job runs Mondays at 9am. It uses the gh CLI to list the last 30 merged PRs in the hermes-agent repo, keeps those from the past 7 days, and checks whether they touched tool, CLI, config or env-var code. For each such PR it checks whether the matching docs page changed in the same PR, then sends a Telegram report.
How it went
The source gives a copy-paste blueprint and no measured results. Output is a list of gaps where code changed but docs didn't. If everything is in sync, the agent replies [SILENT] and nothing is sent.
Worth knowing
The prompt hardcodes this repo's file paths and fetches only 30 merged PRs, so adapt the paths and raise the limit if more than 30 PRs merge in a week.

Try it yourself with Hermes Agent

Every [day and time], check the pull requests merged into [repo name] over the past week. Flag any that changed [tool schemas, CLI commands, config options, or environment variables] and list which docs pages in [docs path] likely need updating. Send me a short report with PR links and stop there without editing any docs.

Read the original ↗

Source: hermes-agent.nousresearch.com · Undated

Five of these in your inbox every morning

The best things people got an AI agent to do, each with the prompt to try it.

More like this