CR Request

Turn "please review this" into a review that can fail. The skill pins what changed, states what the change was for, and hands both to a reviewer who reports, never fixes.

target -> intent -> risk -> brief -> independent review -> verdicts + findings -> record

Arguments are optional: a base ref (commit, branch, tag) and a path to the spec, issue, or plan; missing values are discovered in steps 1 and 2. Chain inputs, when they exist: the spec path, the plan path, the Base line of the plan's ## Execution record, the scope (task <n> or branch), and the Verify: lines of that record. Verify: lines are signals from the caller, not evidence the reviewer gathered. Without a spec or a plan, intent comes from the conversation and commit messages; no journal is written.

1. Pin the target

A review of the wrong diff is worse than no review. Before anything else: