pr-review-response

## Context When an agent fixes code in response to PR review comments (from Copilot, a human reviewer, or any GitHub reviewer), the fix alone is not enough. The reviewer needs to see — on the PR thread itself — which comments were addressed and how. Without replies, comments stay visually unresolved, reviewers must re-read the entire diff to verify fixes, and there's no traceable link between feedback and resolution. Use this skill whenever: - You are fixing code based on PR review feedback - You are addressing Copilot review suggestions - You are responding to reviewer-requested changes on a PR - A squad member hands you review comments to resolve ## SCOPE ✅ THIS SKILL PRODUCES: - Reply comments on each review thread explaining the fix - Optionally resolved threads (via GraphQL when appropriate) - Commit messages that reference the PR and review context ❌ THIS SKILL DOES NOT PRODUCE: - The code fixes themselves (that's the agent's domain work) - New review comments or reviews - PR descriptions or summaries ## Patterns ### Step 1: Read the review comments **Using MCP tools (preferred when available):** ``` github-mcp-server-pull_request_read method: "get_review_comments" owner: "{owner}" repo: "{repo}" pullNumber: {pr_number} ``` This returns review threads with metadata: `isResolved`, `isOutdated`, `isCollapsed`, and their associated comments. Each comment has an `id` you'll need for replies. **Using gh CLI (fallback):** ```bash gh api repos/{owner}/{repo...