PR Review Skill

Review a pull request with context-aware depth based on your relationship to the PR.

Setup

Read ~/.dotfiles/ai/me.md to get:

• •GitHub username
• •Teams you're a member of

Step 1: Gather PR Information

If given a PR number:

gh pr view $ARGUMENTS --json number,title,body,baseRefName,headRefName,reviewRequests,files,additions,deletions,comments,reviews

If given a branch name:

gh pr list --head $ARGUMENTS --json number --jq '.[0].number'
# Then use that number

Step 2: Determine Reviewer Relationship

Check in this order:

1. •Direct reviewer: Check if username is in reviewRequests[].login
2. •Team reviewer: Check if any team from me.md matches reviewRequests[] where typename == "Team"
3. •Codeowner: Parse CODEOWNERS file and check if changed files match user's teams
   bash

   cat .github/CODEOWNERS 2>/dev/null || cat CODEOWNERS 2>/dev/null
   gh pr diff $PR --name-only
   

Step 3: Fetch and Compare

# Fetch the branches
git fetch origin <baseRefName> <headRefName>

# Get the diff
gh pr diff $PR

Step 4: Gather Context

Existing comments (to avoid duplicating feedback):

gh pr view $PR --json comments,reviews

Linked issues (parse from PR body for "Fixes #", "Closes #", etc.):

gh issue view <ISSUE_NUMBER> --json title,body

Step 5: Generate Review

Follow the template in review-template.md for output format.

Focus based on relationship:

Step 6: Local Checkout (on request)

When the user asks to "check it locally" or "set up a worktree":

g wt --pr $PR

This creates a worktree and copies build artifacts automatically.

If the worktree already exists, the command will output the path. Use g co to switch to it:

g co <branch_name>