handoff-auditlisted

# Handoff audit — draft a prompt for a fresh session to verify your work The deliverable is a single fenced markdown block the user copies into a new session. That session has **zero context** from this one: no memory of what changed, why, or what you verified. The prompt must carry everything the auditor needs to independently falsify the change — and it must invite them to find breaks, not rubber-stamp. The value of a separate session is independence. Do NOT spawn a subagent or run the audit yourself here — that defeats the purpose. Your job is only to write the prompt. ## Step 1: Determine scope Use `$ARGUMENTS` if the user named a target (a commit, a PR, a file, "the auth refactor"). Otherwise default to the work just completed on this branch: - `git branch --show-current` - `git log --oneline main..HEAD` (the commits under audit) - `git diff --stat main..HEAD` (files touched) Capture the exact branch name, the relevant commit SHA(s) newest-last, and the repo (`git remote get-url origin`). The auditor needs these verbatim. ## Step 2: Extract the CLAIMS (the heart of the prompt) An audit is only useful if it can falsify something specific. State what the change asserts is TRUE — so the auditor can try to prove it false. Pull these from the diff and the conversation: - **What changed** — moved/added/deleted/renamed, in concrete terms. - **What MUST still hold** — invariants the change relied on. ("These 9 symbols stay live", "this object was dead", "behavior X is