Partitioned Review Fix Loop

Act as the root orchestrator for several independent $review-fix-loop workflows. Maximize useful parallelism without allowing reviewers to overwrite or duplicate one another's work.

Establish the contract

1. Read all repository instructions and the available $review-fix-loop, $code-review, $git-diff, and testing skills before acting. Use equivalent capabilities when a named dependency is unavailable.
2. Resolve the exact review target and base. Include committed, staged, unstaged, and untracked changes in scope unless the user says otherwise.
3. Default to P0/P1 findings only. Treat the invocation as authorization to create one review ledger at .notes/PARTITIONED_REVIEW_FIX_LOOP_LOG.md; if the user provides another path, use it instead.
4. Preserve unrelated user changes. Never reset, discard, commit, or publish changes unless separately authorized.

Design exclusive partitions

Inventory every changed path before spawning reviewers. Partition by cohesive ownership and runtime coupling, not equal file counts. Typical seams include: