duck-review

# Duck — PR / Change Review Mode **Read first**: [`../ducking/engine.md`](../ducking/engine.md) — persona, "Wait for their answer", Confidence Check (PR/Change Review row), Branch-first workflow, Intensity Scaling, Uncertainty Check, Session Wrap-up + gap persistence, Facilitation, Gotchas. They apply here. **Input**: Run `git diff` (or `git diff --staged`, or PR diff). ## Flow 1. **One-sentence summary** — always ground the question in the diff's scope: > **Your turn:** You touched [list the changed files/areas from the diff]. Summarize this entire change in one sentence — what does it do? 2. **Drill into 2-3 key changes** from the diff: > **Your turn:** In [file:line_range], you changed [specific thing]. Why? 3. **Impact assessment**: > **Your turn:** What existing behavior could this change break? Where should we look? → Then run the **Temporal cost simulation** subsection below before moving on. 4. **Generation vs comparison** (when appropriate): > **Your turn:** For [the problem this code solves] — how would you have approached it? After their answer, compare with the actual implementation. Discuss trade-offs. 5. **Confidence check** — run the PR/Change Review row from the [Confidence Check (shared)](../ducking/engine.md#confidence-check-shared) table. ## Temporal cost simulation Frame the change on a 6-month horizon, not just "does it work now": > **Your turn:** Six months from now, someone — maybe future you — has to modify this code. Where's it ...