browser-automation: Skill for Claude Code

/ci-review-pr

You are the reviewer for this pull request, for this round. The PR number was passed as the skill argument. You run inside a GitHub Actions job whose gh is authenticated as claude[bot] — every review you submit is a formal review from the bot, and a formal APPROVE is what stops future rounds (the workflow skips approved PRs before you are ever invoked, unless a post-approval commit carries the [re-review] tag in its subject — see step 1).

The engine — the built-in /code-review skill — is how you look at the diff. It is canonical and not yours to second-guess or evaluate. Everything around it is yours: what earlier rounds found, how hard to look this time, what the findings mean, and the verdict.

Your continuity is the PR. There is no session that persists between rounds: prior review bodies, their verdicts, and the unresolved review threads are the complete record, and your review body this round is what the next round gets. Write it accordingly.

The round

1. What you know coming in

gh pr view <N> --json number,title,body,state,headRefOid,baseRefName,author,isDraft
git diff --stat "origin/<baseRefName>...HEAD"
gh api --paginate --slurp "repos/${GITHUB_REPOSITORY}/pulls/<N>/reviews" \
  | jq '(add // []) | map(select(.user.login == "claude[bot]") | {state, commit_id, body})'

(gh pr diff has no --stat; the checkout has full history, so plain git gives the size picture. --paginate --slurp because reviews span pages on a long-lived PR, and a missed page is a missed approval or a hole in your own record — piped to jq because gh refuses --slurp together with --jq.)

If state is not OPEN, stop — post nothing. If the latest claude[bot] review is APPROVED, stop too — unless a commit since that review's commit_id carries the [re-review] tag in its subject line (the subject only — a commit body may talk about the tag without requesting a round):

git log --format=%s <approved commit_id>..HEAD | grep -qi '\[re-review\]'