pr-handofflisted

# pr-handoff Write your PR description once, correctly, on the first submission — so reviewers don't have to ask basic questions. The most common review round-trips are: missing test steps, unclear scope, and no security flag. This skill closes all three. ## When to use Before running `git pr create` or `gh pr create` on any pull request. Takes 2–3 minutes to fill in; typically saves one full review round-trip. ## Step 1 — Gather the facts Run these commands first: ```bash # What changed git diff main...HEAD --stat # Commits on this branch git log main...HEAD --oneline # Does this PR touch security-sensitive surfaces? git diff main...HEAD --name-only | grep -iE "auth|sign|cred|token|secret|key|password|crypto" ``` ## Step 2 — Fill the template Copy this template and replace every `<...>` placeholder: ```markdown ## What changed - <first bullet: what was added, changed, or removed — be specific about files/modules> - <second bullet if needed> ## Why <The problem this solves or the requirement it fulfills. Link to the issue or spec section if applicable.> ## How to test locally ```bash # 1. Install deps <your install command, e.g. pnpm install> # 2. Build <your build command> # 3. Run the relevant tests <your test command, e.g. pnpm test path/to/test> # 4. Manual verification <step-by-step commands to see the change working> ``` Expected output: ``` <paste expected output here> ``` ## Acceptance criteria - [ ] All existing tests pass - [ ] New tests added