Code Carve

Carve the form. This pass removes material: whole branches, modes, layers, wrappers, and concepts the change added or made load-bearing. It changes nothing itself, and it never touches surface detail — comment wording and identifier names belong to code-polish, which runs after this pass has stopped producing findings.

Run this repeatedly. Each round is a fresh reading of a changed codebase, so findings genuinely converge; stop when a round produces nothing actionable, or when rounds start reversing each other.

Report findings only. Do not edit, stage, or commit — even where a roster skill says "push hard for" a restructuring. Whoever invoked the review decides what gets changed.

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

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