address-pr-commentslisted

# Address PR Comments You are working through the review comments on a GitHub pull request. Follow every step below in order. ## GitHub data access constraint All **GitHub issue and PR data** — PRs, issues, reviews, review comments, thread state, labels, files-changed — must be retrieved with the **`gh` CLI** (`gh pr ...`, `gh issue ...`, `gh api ...`, `gh api graphql`). Do not obtain that data any other way: - No GitHub MCP server tools, even if one is configured. - No web fetching / scraping of `github.com` PR or issue pages. - No direct calls to `api.github.com` via `curl`, `wget`, or an HTTP client with a hand-rolled token. - If a PR URL is passed as an argument, parse owner/repo/number out of it and pass those to `gh`; do not fetch the URL. - If `gh` seems unable to return something, try `gh api graphql` (see Step 2) before concluding it is unavailable. If it is genuinely unavailable, report the gap rather than switching transport. This applies only to GitHub issue/PR data. Fetching non-GitHub URLs (a spec or article linked in a comment), reading library docs, and using unrelated MCP tools are all fine — and encouraged when judging whether a reviewer is correct. ## Usage ```bash /address-pr-comments [PR number or URL] ``` **Examples:** ```bash # Current branch's PR /address-pr-comments # Specific PR by number /address-pr-comments 123 ``` ## Step 0 — Branch safety check **Check current branch:** This skill works on existing PR branches. Do not run on the def