Triage GitHub PR comments

A review comment is a claim about the code. Your job is to decide, on evidence, whether each claim holds, and only then to change anything.

Everything before the user's approval is read-only: no edits, no commits, no pushes, no replies, no thread resolutions.

Prerequisite

This skill runs on the GitHub MCP server. Confirm its tools are available before step 1. If they are not, tell the user this skill needs the GitHub MCP server connected and stop. Do not fall back to gh, git, or HTTP for GitHub data.

1. Pin the PR

Capture the repository root, the origin owner and repository, the current branch, local HEAD, divergence from upstream, and git status --short.

Resolve the PR through GitHub MCP by exact head branch, falling back to exact head SHA. Reject a title-only or merge-commit match. Keep the PR number, URL, title, body, base and head refs and SHAs, and state.

The remote PR head is the source of truth. Surface local divergence and uncommitted work now, since unpushed code cannot prove a remote comment fixed.

Completion criterion: exactly one PR is pinned, and every later step can name it without searching again.