Github Code Review — Review PRs: diffs, inline comments via gh or REST
Github Code Review — Review PRs: diffs, inline comments via gh or REST
Start with meaning, then move to detail.
This lesson explains Github Code Review — Review PRs: diffs, inline comments via gh or REST as part of getting started with Hermes correctly. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, Prerequisites, then verify failure modes and version compatibility.
No prior experience is required; follow the steps on a safe test setup first.
A clear outcome before you read.
- Understand Github Code Review — Review PRs: diffs, inline comments via gh or REST without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Review PRs: diffs, inline comments via gh or REST
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03Prerequisites
Read this after the foundation, then connect it to the previous step.
- 04Setup (for PR interactions)
Read this after the foundation, then connect it to the previous step.
- 051. Reviewing Local Changes (Pre-Push)
Read this after the foundation, then connect it to the previous step.
- 06Get the Diff
Read this after the foundation, then connect it to the previous step.
- 07Review Strategy
Read this after the foundation, then connect it to the previous step.
- 08Review Output Format
Read this after the foundation, then connect it to the previous step.
- 09Code Review Summary
Read this after the foundation, then connect it to the previous step.
- 10Critical
Finish here to verify the result and special cases.
Copy only after you understand the effect.
if command -v gh &>/dev/null && gh auth status &>/dev/null; then
AUTH="gh"
else
AUTH="git"
if [ -z "$GITHUB_TOKEN" ]; then
if _hermes_env="${HERMES_HOME:-$HOME/.hermes}/.env"; [ -f "$_hermes_env" ] && grep -q "^GITHUB_TOKEN=" "$_hermes_env"; then
GITHUB_TOKEN=$(grep "^GITHUB_TOKEN=" "$_hermes_env" | head -1 | cut -d= -f2 | tr -d '\n\r')
elif grep -q "github.com" ~/.git-credentials 2>/dev/null; then
GITHUB_TOKEN=$(uv run python3 "${HERMES_HOME:-$HOME/.hermes}/skills/github/github-auth/scripts/git-credential-token.py")
fi
fi
fi
REMOTE_URL=$(git remote get-url ori# Staged changes (what would be committed)
git diff --staged
# All changes vs main (what a PR would contain)
git diff main...HEAD
# File names only
git diff main...HEAD --name-only
# Stat summary (insertions/deletions per file)
git diff main...HEAD --statgit diff main...HEAD --stat
git log main..HEAD --onelineRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.