GitHub PR Review (cron)
Set up a scheduled GitHub pull-request reviewer that checks a repository on a cron schedule, leaves real review comments on open PRs, and needs no public webhook endpoint, bot app, or inbound network exposure.
Requirements
- Authenticate
ghon the Hermes host. - Terminal tool (for
gh). - Custom review skill (quality depends on this).
- Messaging gateway (for digest delivery).
- Cron.
How to use
No webhook, no public endpoint, no inbound network exposure at all.
Swap --deliver local for --deliver telegram or --deliver discord to also get a digest.
Frequency trade-off: every 30 minutes means faster feedback but more repeated diff-reads. Nightly is cheapest.
Cron sessions are fresh — the agent has no memory of previous reviews. If you want continuity (e.g., 'I already commented on this line'), encode that in the review skill as a rule to check existing comments first.
- Complete GitHub CLI authentication on the Hermes host.
gh auth login # needs repo scope
gh auth status # verify
- Create a review skill that encodes your standards. Drop it in
~/.hermes/skills/pr-review/.
~/.hermes/skills/pr-review/
SKILL.md # review criteria, style rules, what to flag
- Start the gateway so cron runs unattended.
hermes gateway install
- Create the cron job.
hermes cron create "*/30 * * * *" \
"Review open PRs on YOUR_ORG/YOUR_REPO opened or updated in the last
30 minutes. For each one: gh pr diff <num>, evaluate against the
pr-review skill, then post a review comment with gh pr review.
If nothing new, respond [SILENT]." \
--skills pr-review \
--name "PR review (cron)" \
--deliver local
Prompts.
A lighter daily variant that only summarizes instead of auto-commenting.
hermes cron create "0 9 * * *" \
"Daily PR digest for YOUR_ORG/YOUR_REPO. List PRs opened yesterday,
their titles, authors, and a one-line assessment (ready to merge /
needs changes / wip). Post to home channel." \
--name "Daily PR digest" \
--deliver telegram
Source: aliaihub/awesome-hermes-usecases and its contributors. License: CC-BY-4.0. Source license notice.
Translation and editorial adaptation by ClawCases.
>Resources
>Related Use Cases
Agent Merge-Conflict Arbiter
Resolve a git merge conflict between two agents' branches as an impartial third party: a neutral arbiter that takes both diffs and their stated intents and produces a merged result without overwriting either side.
AI-Powered Earnings Tracker
Stay on top of earnings season across dozens of tech companies without manually checking multiple sources and remembering report dates for every AI/tech earnings report.
Second Brain
This workflow turns OpenClaw into a second-brain memory system you feed by text message through Telegram, iMessage, or Discord, backed by a custom searchable Next.js dashboard you can browse anytime.