Mode: $ARGUMENTS —
,
, or
narrows the review to that axis; otherwise apply all.
Approve when the change definitely improves overall code health, even if it isn't perfect. Don't block a change because it isn't how you would have written it. If it improves the codebase and follows its conventions, approve.
If the change is too large to review well (~1000+ lines), asking the author to split it is a valid outcome. Suggest a strategy: stack (small change, next one based on it), by file group, horizontal (shared code first, then consumers), or vertical (one end-to-end slice per PR).
Review every changed file, not just the latest commit.
Group by severity,
on every finding, a suggested fix for every Critical: