gh-review

Review PR #$ARGUMENTS

Review a pull request with proper branch checkout and convention checks.

Tool Usage: This workflow uses the AskUserQuestion tool to confirm review decisions, clarify ambiguous findings, and get approval before submitting reviews.

Process

1. Save current branch:

   git branch --show-current
   

2. Fetch PR details and any existing reviews/comments:

   gh pr view $ARGUMENTS --json title,body,headRefName,baseRefName,additions,deletions,changedFiles,commits,files,reviews
   gh api repos/synaptiai/synapti-marketplace/pulls/$ARGUMENTS/comments
   

3. Fetch PR conversation (general discussion comments):

   gh api repos/{owner}/{repo}/issues/$ARGUMENTS/comments
   

4. Extract and fetch linked issue:

   # Extract issue number from PR body (looks for "closes #X", "fixes #X", etc.)
   gh pr view $ARGUMENTS --json body --jq '.body' | grep -oiE '(closes|fixes|resolves)\s*#[0-9]+' | grep -oE '[0-9]+'
   

   If linked issue found:

   # Fetch full issue with acceptance criteria
   gh issue view {linked-issue} --json title,body,comments
   
   # Fetch all issue comments
   gh api repos/{owner}/{repo}/issues/{linked-issue}/comments
   

5. Cross-reference checklist: Create a verification list from issue acceptance criteria to check against implementation

6. If previous reviews or comments exist: This is a follow-up review. You MUST:

   • Read through ALL previous review comments
   • Track each piece of feedback that was given
   • Later verify each item was addressed (fixed or explained)
   • Note: You're still doing a FULL review - previous reviewers may have missed things

7. Checkout the PR branch (CRITICAL - never review from wrong branch):

   git fetch origin {headRefName}
   git checkout {headRefName}
   

8. Get the full diff:

   gh pr diff $ARGUMENTS
   

9. Read all changed files - use the Read tool on each modified file to understand the full context