HermesBELARABI
العربيةSearch/CheckingSign in
AcademyDirectorySolutionsStudioProjectsCompareSearch Releases Pricing Account Sign in
Academy → Practical GuidesOfficial documentation · Arabic guidance

Tutorial: GitHub PR Review Agent

تطبيق: وكيل مراجعة طلبات الدمج

Intermediate7 min readLesson 115 questions✓ 2026-08-18
Before you read

What this page is, and what it holds.

This page covers Tutorial: GitHub PR Review Agent. It carries a source warning and takes about 7 minutes to read. A skill is text the agent obeys. Read it before enabling it.

10sections
17code examples
1tables
6commands
1,247source words
The official one-line description

Build an automated AI code reviewer that monitors your repos, reviews pull requests, and delivers feedback — hands-free

What you will be able to do

Outcomes taken from this page, not a template.

  • Understand what Skill is and when you need it.
  • Run hermes cron list and hermes cron create and understand what happens next.
  • Read the table and take only the row that applies to you.
  • Set REQUEST_CHANGES in the right place.
Identifiers you will meet

Exactly as they appear in Hermes.

Commands
  • hermes cron list
  • hermes cron create
  • hermes gateway
  • hermes gateway status
  • hermes gateway install
  • hermes cron run pr-review
Environment variables
  • REQUEST_CHANGES
  • YOUR_REVIEW
Page map

Jump to the part you need.

  1. 01Prerequisites
  2. 02Step 1: Verify the Setup
  3. 03Step 2: Try a Manual Review
  4. 04Step 3: Create a Review Skill
  5. 05Step 4: Teach It Your Conventions
  6. 06Step 5: Create the Automated Cron Job
  7. 07Step 6: Run It On Demand
  8. 08Going Further
  9. 09Troubleshooting
  10. 10What's Next?
The full official page

Nothing summarised away.

The documentation body below is reproduced from the official source so commands and identifiers stay exact. Each section carries a short note describing what it contains.

The problem: Your team opens PRs faster than you can review them. PRs sit for days waiting for eyeballs. Junior devs merge bugs because nobody had time to check. You spend your mornings catching up on diffs instead of building.

The solution: An AI agent that watches your repos around the clock, reviews every new PR for bugs, security issues, and code quality, and sends you a summary — so you only spend time on PRs that actually need human judgment.

What you'll build:

Text9 lines
┌───────────────────────────────────────────────────────────────────┐
│                                                                   │
│   Cron Timer  ──▶  Hermes Agent  ──▶  GitHub API  ──▶  Review     │
│   (every 2h)       + gh CLI           (PR diffs)       delivery   │
│                    + skill                             (Telegram, │
│                    + memory                            Discord,   │
│                                                        local)     │
│                                                                   │
└───────────────────────────────────────────────────────────────────┘

This guide uses cron jobs to poll for PRs on a schedule — no server or public endpoint needed. Works behind NAT and firewalls.

---

Prerequisites

Ordered, practical steps. Run one and confirm it worked before moving on. Commands here: hermes gateway install, hermes gateway.

Shell3 lines
  hermes gateway install   # Install as a service
  # or
  hermes gateway           # Run in foreground
  • GitHub CLI (gh) installed and authenticated:
Shell6 lines
  # Install
  brew install gh        # macOS
  sudo apt install gh    # Ubuntu/Debian

  # Authenticate
  gh auth login

---

Step 1: Verify the Setup

Ordered, practical steps. Run one and confirm it worked before moving on.

Make sure Hermes can access GitHub. Start a chat:

Shell1 line
hermes

Test with a simple command:

Text1 line
Run: gh pr list --repo NousResearch/hermes-agent --state open --limit 3

You should see a list of open PRs. If this works, you're ready.

---

Step 2: Try a Manual Review

Ordered, practical steps. Run one and confirm it worked before moving on.

Still in the chat, ask Hermes to review a real PR:

Text4 lines
Review this pull request. Read the diff, check for bugs, security issues,
and code quality. Be specific about line numbers and quote problematic code.

Run: gh pr diff 3888 --repo NousResearch/hermes-agent

Hermes will:

  1. Execute gh pr diff to fetch the code changes
  2. Read through the entire diff
  3. Produce a structured review with specific findings

If you're happy with the quality, time to automate it.

---

Step 3: Create a Review Skill

Ordered, practical steps. Run one and confirm it worked before moving on.

A skill gives Hermes consistent review guidelines that persist across sessions and cron runs. Without one, review quality varies.

Shell1 line
mkdir -p ~/.hermes/skills/code-review

Create ~/.hermes/skills/code-review/SKILL.md:

MARKDOWN28 lines
---
name: code-review
description: Review pull requests for bugs, security issues, and code quality
---

# Code Review Guidelines

When reviewing a pull request:

## What to Check
1. **Bugs** — Logic errors, off-by-one, null/undefined handling
2. **Security** — Injection, auth bypass, secrets in code, SSRF
3. **Performance** — N+1 queries, unbounded loops, memory leaks
4. **Style** — Naming conventions, dead code, missing error handling
5. **Tests** — Are changes tested? Do tests cover edge cases?

## Output Format
For each finding:
- **File:Line** — exact location
- **Severity** — Critical / Warning / Suggestion
- **What's wrong** — one sentence
- **Fix** — how to fix it

## Rules
- Be specific. Quote the problematic code.
- Don't flag style nitpicks unless they affect readability.
- If the PR looks good, say so. Don't invent problems.
- End with: APPROVE / REQUEST_CHANGES / COMMENT

Verify it loaded — start hermes and you should see code-review in the skills list at startup.

---

Step 4: Teach It Your Conventions

Ordered, practical steps. Run one and confirm it worked before moving on.

This is what makes the reviewer actually useful. Start a session and teach Hermes your team's standards:

Text4 lines
Remember: In our backend repo, we use Python with FastAPI.
All endpoints must have type annotations and Pydantic models.
We don't allow raw SQL — only SQLAlchemy ORM.
Test files go in tests/ and must use pytest fixtures.
Text3 lines
Remember: In our frontend repo, we use TypeScript with React.
No `any` types allowed. All components must have props interfaces.
We use React Query for data fetching, never useEffect for API calls.

These memories persist forever — the reviewer will enforce your conventions without being told each time.

---

Step 5: Create the Automated Cron Job

Ordered, practical steps. Run one and confirm it worked before moving on. Commands here: hermes cron list, hermes cron create.

Now wire it all together. Create a cron job that runs every 2 hours:

Shell24 lines
hermes cron create "0 */2 * * *" \
  "Check for new open PRs and review them.

Repos to monitor:
- myorg/backend-api
- myorg/frontend-app

Steps:
1. Run: gh pr list --repo REPO --state open --limit 5 --json number,title,author,createdAt
2. For each PR created or updated in the last 4 hours:
   - Run: gh pr diff NUMBER --repo REPO
   - Review the diff using the code-review guidelines
3. Format output as:

## PR Reviews — today

### [repo] #[number]: [title]
**Author:** [name] | **Verdict:** APPROVE/REQUEST_CHANGES/COMMENT
[findings]

If no new PRs found, say: No new PRs to review." \
  --name "pr-review" \
  --deliver telegram \
  --skill code-review

Verify it's scheduled:

Shell1 line
hermes cron list

Other useful schedules

ScheduleWhen
0 */2 * * *Every 2 hours
0 9,13,17 * * 1-5Three times a day, weekdays only
0 9 * * 1Weekly Monday morning roundup
30mEvery 30 minutes (high-traffic repos)

---

Step 6: Run It On Demand

Ordered, practical steps. Run one and confirm it worked before moving on. Commands here: hermes cron run pr-review.

Don't want to wait for the schedule? Trigger it manually:

Shell1 line
hermes cron run pr-review

Or from within a chat session:

Text1 line
/cron run pr-review

---

Going Further

Carries a warning. Read it before running anything here. Commands here: hermes cron create. The upstream warning appears below.

Post Reviews Directly to GitHub

Instead of delivering to Telegram, have the agent comment on the PR itself:

Add this to your cron prompt:

Text4 lines
After reviewing, post your review:
- For issues: gh pr review NUMBER --repo REPO --comment --body "YOUR_REVIEW"
- For critical issues: gh pr review NUMBER --repo REPO --request-changes --body "YOUR_REVIEW"
- For clean PRs: gh pr review NUMBER --repo REPO --approve --body "Looks good"

Weekly PR Dashboard

Create a Monday morning overview of all your repos:

Shell15 lines
hermes cron create "0 9 * * 1" \
  "Generate a weekly PR dashboard:
- myorg/backend-api
- myorg/frontend-app
- myorg/infra

For each repo show:
1. Open PR count and oldest PR age
2. PRs merged this week
3. Stale PRs (older than 5 days)
4. PRs with no reviewer assigned

Format as a clean summary." \
  --name "weekly-dashboard" \
  --deliver telegram

Multi-Repo Monitoring

Scale up by adding more repos to the prompt. The agent processes them sequentially — no extra setup needed.

---

Troubleshooting

A troubleshooting section. Find the symptom that matches yours rather than reading it end to end. Commands here: hermes gateway status, hermes cron list.

"gh: command not found"

The gateway runs in a minimal environment. Ensure gh is in the system PATH and restart the gateway.

Reviews are too generic

  1. Add the code-review skill (Step 3)
  2. Teach Hermes your conventions via memory (Step 4)
  3. The more context it has about your stack, the better the reviews

Cron job doesn't run

Shell2 lines
hermes gateway status    # Is the gateway running?
hermes cron list         # Is the job enabled?

Rate limits

GitHub allows 5,000 API requests/hour for authenticated users. Each PR review uses ~3-5 requests (list + diff + optional comments). Even reviewing 100 PRs/day stays well within limits.

---

What's Next?

Explains the idea itself. Read it slowly; the later sections build on it.

Knowledge check

5 questions answered by this page alone.

Every option is a real identifier from the Hermes documentation. The wrong ones are real too, just from other pages.

1. According to this lesson, which command does “Install as a service”?
2. According to this lesson, which command does “Run in foreground”?
3. In this lesson's table, what is the “When” for “0 /2”?
4. Which of these environment variables actually appears in this lesson?
5. Which warning does the source state in this lesson?
Continue from here

Pages this one connects to.