Review someone's pull request as the user and leave inline comments only on GitHub. The comments go out under the user's name, so every one of them has to be correct, critical, and worth a colleague's attention. A short review of three real bugs beats a long one with ten opinions.

The analysis reuses the two axes from the code-review skill (sibling ../code-review/SKILL.md): Standards and Spec. This skill adds a risk lens, a strict ranking gate, a GitHub comment format, and a draft → approve → post loop.

scripts/gh_review.py handles the mechanical parts: listing existing threads, checking line anchors against the diff, rendering the draft, and posting. GitHub rejects a whole review with a 422 error if any comment points at a line outside the diff, so let the script validate anchors instead of guessing.

Process

1. Resolve the PR

Accept a URL, owner/repo#N, or a bare number (bare number = repo in the current directory). Then fetch:

gh pr view <N> -R <owner/repo> --json url,title,body,headRefOid,baseRefName,headRefName,closingIssuesReferences,files

Record headRefOid. Every comment anchors to this SHA.

Code access. If the current directory is a clone of the same repo (gh repo view --json nameWithOwner), run git fetch origin pull/<N>/head and work from git diff origin/<base>...FETCH_HEAD. Read full files with git show <sha>:<path>. Otherwise use gh pr diff <N> -R <repo> and read files with gh api -H "Accept: application/vnd.github.raw" "repos/<repo>/contents/<path>?ref=<sha>". Don't check out the branch or touch the user's working tree.

github-review

Process

1. Resolve the PR