Review GitHub PRs with a structured agent checklist

Use Hermes to inspect pull request diffs, rank issues by severity, and turn the workflow into a scheduled repo watcher.

Done with Hermes Agentยท Intermediate

What they did
A developer used Hermes Agent with the gh CLI already signed in and the Hermes gateway active. They first asked it in chat to pull a PR diff and produce a review, then shaped that into a code-review skill with severity-based output and team rules stored in memory. After that, a cron job ran every 2 hours to scan recent pull requests in chosen repos and send a digest to Telegram.
How it went
The setup did not report any actual review findings. It did note that the stored conventions made the feedback less generic, and it estimated about 3 to 5 GitHub API calls for each PR checked.
Tips
If you want comments posted back to GitHub, make sure the authenticated gh account is the one you want represented. Also confirm the token has repo scope before letting the agent publish anything.

Try it yourself with Hermes Agent

Review the pull request at [PR URL]. First, summarize any bugs, security concerns, and code quality problems in separate sections, and include file and line references plus a severity label for each item. Then help me package this into a reusable check for [repo name] that runs every [interval] and sends a short summary to [destination]. Show me the plan and pause for my approval before you post any comments, submit anything, or make any other irreversible change.

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

Read the original on hermes-agent.nousresearch.com โ†—

1 more report of this

Get 3 agent uses like this every morning

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