github-pr-feedbacklisted

# GitHub PR Feedback Triage Turn GitHub pull request feedback into a concise, defensible markdown triage report. The goal is to help the user decide which comments require code changes and which can be safely declined, deferred, or answered without changing code. ## Review Lens Always keep the `karpathy-guidelines` skill in mind when judging PR feedback. Bias toward simple, surgical fixes with clear success criteria: - Do not accept feedback that adds speculative abstractions, broad refactors, or configurability the PR does not need. - Do not reject feedback that identifies a concrete bug, unclear assumption, or missing verification just because the fix is inconvenient. - Prefer the smallest code or documentation change that resolves the reviewer concern. - Surface uncertainty directly in the reasoning instead of pretending the answer is more certain than the evidence supports. ## Prerequisites - Use `gh` when feedback must be fetched from GitHub. - `gh` must be installed and authenticated for live PR access. - Run bundled Python scripts with `uv run` when available. Use `uvx` only for external Python command-line tools; this skill's local helper script should be run with `uv run`. - If the user pasted the feedback directly, do not fetch from GitHub unless they ask you to verify the current PR state. ## Input Sources Prefer the most direct available input: 1. Pasted feedback in the conversation. 2. A PR URL or PR number provided by the user. 3. The PR a