agentic-harness: Skill for Claude Code

Review PR

You are reviewing a pull request. The user has pointed you at a specific PR; your job is to read it, judge it against the conventions in .claude/rules/, and post a useful review comment.

This skill is intentionally simpler than ship-pr. The PR review job is mostly judgement, which means most of the work is reading and thinking, not running scripts. The script in this skill posts the comment; you draft what it says.

Step 0 — Resolve the PR number

# $ARGUMENTS may be a number (123) or a URL (https://github.com/org/repo/pull/123)
PR_INPUT="$ARGUMENTS"

if [[ "$PR_INPUT" =~ ^[0-9]+$ ]]; then
  PR="$PR_INPUT"
elif [[ "$PR_INPUT" =~ /pull/([0-9]+) ]]; then
  PR="${BASH_REMATCH[1]}"
else
  echo "Could not parse PR number from: $PR_INPUT" >&2
  exit 1
fi

# Confirm we're in the right repo
gh repo view --json nameWithOwner -q .nameWithOwner

If the PR isn't in the current repo, stop. Cross-repo review needs --repo and the user should be explicit.

Step 1 — Gather PR metadata

# Title, body, branch, base, author, state, CI
gh pr view "$PR" --json title,body,headRefName,baseRefName,author,state,statusCheckRollup,reviewDecision,additions,deletions,changedFiles,createdAt

Read it. Note:

• Size — > 500 lines changed is hard to review well. Flag it
• CI status — if checks are failing, that's the first thing to mention
• Existing reviews — has someone already reviewed? Don't repeat their points
• Description quality — is the why in the body, or just the what?

Step 2 — Read the diff

gh pr diff "$PR"

For very large PRs, narrow:

gh pr diff "$PR" --name-only          # Just the file list
gh pr diff "$PR" -- path/to/file      # Single file

Read the whole diff before forming an opinion. Don't just spot-check.

Step 3 — Run the review checklist

Walk through each category. Note specific files and line numbers for each finding so the author can act without hunting.

Conventions