Code Review

15.6. Code Review — Reviewing Your Own Code and Other People’s

Three basic review methods via the CLI

# Review uncommitted changes in the current repo
hermes chat -q "Review my uncommitted changes, list the problems and suggest improvements"

# Clean output mode, suitable for cron/CI (only prints the final report)
hermes -z "review the diff in current git repo and output structured findings"

# Specify a particular model/provider for the review
hermes chat -q "review this PR" --provider anthropic --model claude-opus-4.7

Handling many files in parallel with subagents

For a large, multi-file PR, the review can be split up and delegated to subagents running in parallel via delegate_task — each subagent reviews a part, and the results are merged into a consolidated report, much faster than reviewing file by file sequentially.

Automating the entire review lifecycle

The difference from just using Claude Code/Cursor for manual review in the IDE: Hermes can trigger reviews automatically via GitHub events (hermes webhook subscribe), run periodic scans for new PRs (hermes cron), and then send the results via the Gateway to Telegram/Slack — nobody needs to proactively open the IDE to get a review.

Notes

• For reviews that need to go into a CI/cron pipeline, always use clean output mode (hermes -z or equivalent) so the results can be parsed automatically, without being mixed in with interactive conversation.
• Attach the team’s specific review checklist to AGENTS.md or a dedicated skill (10.4, using /learn from existing coding convention docs) — ensuring reviews are consistent across runs, without relying on the model guessing the criteria each time.
• When having the agent review its own PR (after creating it in 15.5), treat this as a supplementary step, not a replacement for human review — especially for changes that affect security or important business logic.