pull-feedbacklisted

# Git Pull Feedback ## Overview Pulls review feedback on a PR the user authored into a working doc with per-thread triage slots. The point is rigor: every unresolved thread gets a tentative verdict (valid / invalid / nice-to-have / needs-clarification) with reasoning and a plan, so the user can work through feedback deliberately instead of rubber-stamping. **Announce:** "Using git:pull-feedback to pull and triage feedback on PR #N." ## Workflow ### 1. Fetch ```bash ./fetch.sh [ref] ``` `ref` accepts a bare number, `#N`, `owner/repo#N`, a PR URL, or nothing (auto-detects from current branch). The script writes a skeleton doc to `.scratch/pr-reviews/<N>/threads.md` with `_pending triage_` placeholders and prints counts on stdout. Use this output location — don't invent your own filename. ### 2. Orient only if context is cold Add a `## Summary` section (1-2 sentences on what the PR does + state of the review) **only if** you don't already know the PR. If the user has been discussing it in conversation or the branch name tells you, skip — guessing wastes tokens and risks confabulation. ### 3. Triage each unresolved thread (shallow pass) Each thread has a unique `<!-- thread: N -->` anchor. If a reviewer left feedback as a review body instead of (or in addition to) inline comments, it appears in its own `## Review comments` section with a `<!-- review: N -->` anchor per review — triage those the same way. Use targeted `Edit` calls to fill three slots per thread or revie