code-review

Before asking, read User Questions.

Code Review

For an authorized review-and-fix cycle, read ../../shared/adversarial-loop.md for convergence and stop rules. A review-only request remains read-only; a clean loop does not replace this skill's evidence, artifact, and completion/discovery gates.

Challenge Resolve is opt-in: a Code Review invocation alone does not authorize the challenge-resolve skill or an additional iterative adversarial review-and-fix loop. When one would help and the user has not expressly requested or approved it, explain its bounded scope and ask before entering that workflow or loop. Existing explicit approval for the same scope remains valid; do not ask again. Ordinary candidate validation, configured reviewer/challenger inspection and required checks stay within Code Review; they never silently escalate into repeated resolution rounds. A reviewer role named challenger is not authorization to invoke Challenge Resolve. Preserve read-only review and all existing completion gates if the user declines the optional loop.

Run tiered review with strict output gates.

Apply the shared Proportional Execution policy when choosing direct analysis or a detailed workflow; this review's source, coverage, artifact, and completion gates still govern a selected detailed route.

Input Schema

{
  "scope": "optional working-tree|path|commit|pr; infer pr for bare number, #number, or PR URL",
  "target": "optional path, commit ref, PR number, PR URL, or current branch PR",
  "done_when": "blocking issues are identified with gate decision"
}

Scope And Routing

• working-tree: review unstaged/staged local changes.
• path: review one file/directory diff.
• commit: review git diff revision spec, such as COMMIT^!, BASE..HEAD, or BASE...HEAD.
• pr: review open pull request: collect GitHub PR metadata/review evidence, fetch target and PR commits, inspect the verified local checkout; target may be PR number, URL, or current-branch PR.