PR review

/code-review finds the problems. This skill decides which of them are worth a reviewer's attention, and posts them in the shape a human can skim.

Do not review the diff yourself. Running your own pass alongside /code-review gives you two sets of findings with different standards behind them, and no way to rank one against the other.

1. Resolve the target

PR="${1:-$(gh pr view --json number -q .number)}"
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
ME=$(gh api user -q .login)
SHA=$(gh pr view "$PR" --json headRefOid -q .headRefOid)

If gh pr view finds no PR for the current branch, stop and say so.