review-reply

## Identify Target PR Parse `$ARGUMENTS` to extract a PR number or URL. If not provided, detect from the current branch: ``` gh pr view --json number --jq '.number' 2>/dev/null ``` If no PR is found, ask the user to specify one. ### Verify the working tree matches the PR head An explicitly named PR (`/review-reply 42`) may have nothing to do with the currently checked-out branch. Every evidence step below reads the **local working tree**, so reading the wrong revision would quote unrelated code as "verbatim evidence", misclassify live comments as outdated, and land approved fixes on the wrong branch. Silently reading the wrong revision is the one failure mode that makes every downstream quote in this skill a lie. Check **both** conditions before reading anything: ``` gh pr view {number} --json headRefOid --jq '.headRefOid' # PR head git rev-parse HEAD # local HEAD git status --porcelain # uncommitted changes ``` **1. Head mismatch** (`headRefOid` ≠ `HEAD`). Tell the user which branch the PR points at, and pick one: - **Check out the PR branch** (`gh pr checkout {number}`), then proceed normally. Preferred. - **Read at the PR head without checking out.** The head commit of a fork or an unfetched branch is NOT in the local object store, so fetch it first — otherwise `git show` fails with `fatal: bad object`: ``` git fetch origin pull/{number}/head ``` Then quote all evidence from `gi...