code-reviewlisted

# Code Review Four review modes, each a different moment and posture. Pick by when the review happens and who's giving vs receiving it. ## When to use - **pre-merge** (default) — before merging a PR/change: two-axis review, Standards (repo conventions + smell baseline) and Spec (faithful to the originating issue/spec) - **in-flight** — during implementation, before a decision stands: adversarial cross-examination biased to disprove, not approve - **evidence-gate** — before claiming a task done/fixed/passing: produce fresh verification evidence, not assertion - **receiving** — when review feedback arrives: verify the feedback is correct before acting on it; technical rigor over performative agreement - Triggers on "review this", "code review", "before merge", "代码审查", "合并前审查", "帮我看看这代码", "能合并吗", "are you sure", "verify before done", "收到评审意见" **Not for:** deep security review (use `security-review`); machine-detectable lint/style (use `linting`); runtime behavior bugs (use `debugging`). ## Steps ### 1. Pick the mode - Merging a PR / evaluating a diff → **pre-merge** (Step 2) - Mid-implementation, a non-trivial decision is about to stand → **in-flight** (load [references/review-modes.md](references/review-modes.md) §in-flight) - About to claim "done" / "fixed" / "passing" → **evidence-gate** (load [references/review-modes.md](references/review-modes.md) §evidence-gate) - Review feedback just arrived and you're deciding whether to act on it → **receiving** (load [references