review-before-commitlisted

# Review Before Commit No commit until an independent review of the working-tree state has run and converged. Review-then-commit, never commit-then-review: a flaw must be able to block the landing, which matters most where commits go straight to the main branch. ## When to Apply - About to run `git commit` on a non-trivial change - "commit this" / "land this change" / "ship it" ## Workflow ### 1. Get the tree green first Run the project's gates (typecheck, lint, tests) before launching any review. Reviewing a red tree wastes the reviewer on problems the gates already catch. ### 2. Launch independent background reviews - Use the `/rubber-duck-review` skill when installed: it defines reviewer selection, read-only sandboxing, background launch with streaming, and verdict extraction. - Prefer reviewers independent of yourself (a different model); two independent reviewers beat one when available. - Reviewers must run NON-WRITING (a read-only sandbox or plan mode). A writable reviewer has been seen writing a probe test file into the reviewed tree (it ran in the suite and inflated the pass count) and mutating source in place to check tests can fail, then restoring imperfectly. If a review ran writable anyway, diff every modified file before committing. - Start reviews together in the background and keep working; never sleep or poll waiting for them - react to the completion notification, or run a reviewer synchronously when nothing can proceed without its verdict. (In orche