Code Review

Use for local changes, PR changes, or review loops. Read references/repository.md first, then changed-surface instructions. Reviewer lanes report findings only; change owner makes fixes.

Review budget

Accept optional max-turns=<positive integer>; default to 10. Reject missing, zero, negative, non-integer, or malformed values before first pass. There is no upper bound. Count each complete review pass against this budget; when exhausted without RESULT: PASSED, stop with current evidence and ask whether to start a new explicitly authorized run. Never extend automatically.

1. Select effective review scope

Review current intended change, not only HEAD:

1. identify base from explicit target, PR metadata, or repository default; ask if ambiguous;
2. compute committed range base...HEAD;
3. union staged (git diff --cached), unstaged (git diff), and intended untracked files;
4. recompute union before every pass and after every fix.

Unchanged code is evidence only when effective diff causes risk. Preserve unrelated working-tree changes.