What GitHub is for
The official review tutorial combines Hermes, the GitHub CLI, skills, and scheduled polling. It offers a useful pattern for repository monitoring without requiring a public webhook endpoint. Start with a bounded read-only issue or pull-request review before enabling comments or other writes. Keep every finding linked to an exact issue, diff, or commit so a maintainer can assess the conclusion.
What you need
- Access to the intended repository through an authenticated GitHub CLI or a documented MCP server.
- The required Hermes tools and a clear repository, date range, retrieval limit, and permission boundary.
Set it up
- 1
Confirm the authenticated account and repository scope using a harmless read. Select polling for a simple first version; evaluate webhooks separately if immediate event handling is necessary.
- 2
Retrieve a small sample, deduplicate related reports, and distinguish observed symptoms from hypotheses. Save review output locally before authorizing delivery or comments.
Check it works
- Compare the summary against original issues and current diffs. Confirm pagination and access limitations are visible.
- Refresh the pull request before any authorized comment so the review does not target an obsolete revision.
Limits and failure points
- An issue being closed or a fix being merged does not prove the change shipped in a release.
- Automated review is advisory. Posting, labeling, merging, and publishing require their own action rules and account permissions.
Primary sources
Spotted something wrong or out of date? Tell us on X at @HermesWatcher (opens in a new tab) and we will fix it.