pr-reviewlisted

# PR/MR Review Structured code review for a merge or pull request. Fetches ticket requirements when available, reviews the code and posts inline comments. **You submit the review.** Throughout this skill "change" is the generic term for what the host calls a merge request (GitLab) or pull request (GitHub, Bitbucket) — the host adapter keeps that host's own word when naming the concrete API object or CLI call. Likewise "ticket" is the generic term for whatever the tracker holds (a JIRA issue, a GitHub issue). The workflow is host- and tracker-agnostic; the host-specific and tracker-specific mechanics live in adapter files under `references/` and load only when you reach the step that needs them. This keeps the always-loaded body focused on judgment — the review itself, which is the same regardless of where the code and the ticket happen to live. ## Workflow Work through steps in order. Prioritize reading the diff over full files — fetch full file content only when the diff lacks enough context to make a confident judgment. ### Step 1 — Identify the host and load its adapter Determine which host the change lives on, primarily from the URL shape: - `…/-/merge_requests/<n>` → GitLab → read `references/hosts/gitlab.md` - `github.com/<owner>/<repo>/pull/<n>` → GitHub → read `references/hosts/github.md` The adapter file is the authority for that host's mechanics: URL parsing, auth check, the exact calls to fetch metadata/diffs, the local-clone path convention, and how to po