handofflisted

# Handoff — verify you understood Claude's code When Claude builds a feature, it is easy to merge the result without truly reading or understanding it. `handoff` turns passive review into an active check: it interviews the developer to confirm they read the code (where the logic lives) and understood it (why decisions were made, how it behaves), then reports a score and the spots to revisit. This skill conducts an interactive quiz. Ask questions **one at a time** and wait for an answer before continuing. Conduct the entire quiz in the developer's language (match the language they are writing in). ## Step 1 — Gather the material (hybrid source) Build the quiz from two complementary sources: 1. **Conversation context** — what was built this session: the files touched, the key decisions and trade-offs, what was deliberately NOT done, and what could plausibly break. This is the source for the "why". 2. **Git diff (when available)** — to objectively anchor "where" and check that nothing important is missed. Run: - `git rev-parse --git-dir` to confirm a repo exists. - `git diff --stat` then `git diff` (covers unstaged + staged) to enumerate changed files and lines. Use real `file:line` locations from this diff. If there is no git repo, degrade gracefully and rely on conversation context alone — still produce a useful quiz. ## Step 2 — Calibrate the number of questions Scale to the size of the change (use the diff stat, or your best estimate from co