gh-pr-review

When running a PR code review, follow the process outlined here. ## Pre-requisites - gh CLI: !`which gh` - jq: !`which jq` If `gh` is not found, inform the user it must be installed and configured; if `jq` is not found, inform the user it must be installed. In either case, immediately stop. ## Project Context - current branch: !`git branch --show-current` - default branch: !`git symbolic-ref --short refs/remotes/origin/HEAD` - changed files: !`gh pr diff --name-only` ## Step 1: Validate PR State If `changed files` is empty or `gh pr view --json number,url` fails, inform the user no reviewable PR exists for the current branch and stop. ## Step 2: Run Code Review Invoke the `/code-review` skill to perform the full code review. Pass along any user-provided focus areas or context from the original arguments. After /code-review completes, proceed immediately to Step 3 — do not stop here. ## Step 3: Offer to Post Review to GitHub Ask the user whether they'd like to post the review to the PR on GitHub using `AskUserQuestion` with options "Yes, post the review to GitHub" and "No, just the local review". If the user declines, proceed to Step 5. If the user accepts: 1. Gather PR metadata by running `${CLAUDE_SKILL_DIR}/scripts/pr-metadata.sh`, which outputs JSON with `owner_repo`, `pr_number`, `head_sha`, `pr_author_login`, and `current_user_login`. 2. Build the review body from: Review Summary table, Review Recommendation, What's Good section, and all findings organized b...