PR-Review: gate GitHub pull requests — inspect CI and diff, approve or request changes, then squash-merge only when the gate is green. On REQUEST_CHANGES or any hold, always write Why (lens + evidence) and Next steps (author-actionable) on the GitHub review and in the chat report. Use when the user wants to review and merge a PR, batch-review PRs, re-review after changes requested, or run a CODEOWNER merge pass (especially Book-IQ/frs).