Code Polish

Finish the surface. Every finding here changes how the code reads — comment wording, doc prose, identifier names — and none of them change what it does. This is the last pass, run once, after structural review has stopped producing findings.

The order matters and is not a preference. Carving removes material; polishing works the final surface. Polish a form that is still wrong and the work is wasted when the form changes. So if a finding here needs a code change to fix properly, it is not a polish finding — it goes in Deferred and the structural review owns it.

Target

Scope comes from the invocation arguments or request ($ARGUMENTS):

• empty → uncommitted changes plus the current branch's diff vs its base
• a path → that file or directory tree
• a commit, range, branch, or PR number → that diff; for a single commit, compare against its first parent
• --fix anywhere in the args → apply the collated findings after reporting; otherwise report only

Resolve the scope once, and give every reviewer the same scope plus the same base revision. Without a shared base a reviewer cannot tell what the change introduced from what was already there, and the findings stop lining up. Never hand a reviewer bare paths with no base revision.

Roster