pr-review

MANDATORY: Load the humanizer skill (albino:humanizer) now and keep all its rules active for the entire session. Every piece of text you write or post, including comment bodies, the review body, and any output to the user, must pass the humanizer check before it leaves your context.

PR Review

Review the GitHub pull request: $ARGUMENTS

If the line above still shows a placeholder instead of a value, this platform does not pass arguments to skills: take the value from the user's message instead, and treat it as empty when the message gives none. Read every later mention of the placeholder as that value.

Step 1: Validate Input

If $ARGUMENTS is empty or missing, stop immediately and tell the user:

Usage: /pr-review <github-pr-url>
Example: /pr-review https://github.com/owner/repo/pull/123

Parse owner, repo, and number from $ARGUMENTS now (URL format: https://github.com/{owner}/{repo}/pull/{number}). If the URL does not match this format, stop and show the usage message above.

Step 2: Pre-Review Gate

Run both in parallel:

gh pr view "$ARGUMENTS" --json state,isDraft,author --jq '{state: .state, isDraft: .isDraft, author: .author.login}'

gh api repos/{owner}/{repo}/pulls/{number}/reviews --jq '[.[].user.login]'

Stop immediately with a clear message if any condition is true:

• state is not "OPEN" (PR is closed or merged)
• isDraft is true
• author.login ends in [bot] or is one of: dependabot, renovate, snyk-bot, github-actions
• The authenticated user's login already appears in the reviews list (run gh api user --jq '.login' to get it if needed)

Step 3: Fetch PR Data

Run all three in parallel:

gh pr view "$ARGUMENTS" --json number,title,body,author,baseRefName,headRefName,headRefOid,state,additions,deletions,changedFiles

gh pr view "$ARGUMENTS" --json files --jq '[.files[].path]'

gh pr diff "$ARGUMENTS"

If any command fails, stop and report the error. If not authenticated, suggest gh auth login.