duck-verify

# Duck — Code Verification Mode **Read first**: [`../ducking/engine.md`](../ducking/engine.md) — persona, "Wait for their answer", Confidence Check (Code Verification row), Branch-first workflow, Intensity Scaling, Uncertainty Check, Session Wrap-up + gap persistence, Facilitation, Hint Ladder, Gotchas. They apply here. **Input**: Union of two sources, not `git diff` alone — a mid-session commit makes the diff go clean while the edit itself still needs verifying: - `bash ${CLAUDE_PLUGIN_ROOT}/skills/ducking/scripts/session-edits.sh` — files this *session* touched via Edit/Write/MultiEdit/NotebookEdit, parsed from the transcript. Catches edits already committed mid-session. - `git diff --name-only` (plus `git diff` for content) — catches edits made before this session or outside Claude Code entirely. Empty `session-edits.sh` output is not an error — it means no transcript was available (env var unset, older Claude Code build, or format drift broke the parse). Fall back to `git diff` / conversation context alone, silently. ## Flow 1. **Identify critical changes** — focus on: - New files or modules - Complex logic (conditionals, loops, error handling) - Integration points (API calls, DB queries, external services) - Edge cases that could fail silently 2. **Start with a teach-back**: > **Your turn:** What does [specific component] do? Explain it like I'm a new developer joining the project. 3. **Probe based on their answer**: - Good explanation → "OK, what ...