/pr-review

Review a pull request before it merges — yours or a colleague's. This is /continue step 10 as a standalone command, and the inline form of the future ai-pr-review.yml CI workflow.

Steps

1. Resolve the PR. Default to the PR for the current branch; accept an explicit #N argument otherwise. Fetch the diff, the linked Issue, and the CU-id.
2. Run code-reviewer over its ten-point checklist: architecture fit, test coverage, contract changes, secrets, backward-compat, PR size, auth surface, dependencies, CLAUDE.md adherence, overengineering.
3. Route domain findings to the owner — code-reviewer is the generalist; for a finding in a specialist's domain, name the owning agent so the developer can pull it in:
   • auth / tokens / RBAC → auth-security
   • money flows → payments
   • DTO / RPC / FE-BE shape → contracts-schema
   • schema / indexes / migrations → database
   • PII / data flows → privacy-compliance
4. Report findings grouped by severity (blocker / should-fix / nit) with file:line references. Post as a review if the developer asks; otherwise summarize inline.

Boundaries

• Does not merge. Review only — merge stays a human (or explicitly-configured) action.
• A blocker finding means the PR is not ready for review/merge until addressed.