gh-address-commentslisted

# GitHub PR Comment Handler Use this skill when the user wants to work through requested changes on a GitHub pull request. Use the GitHub app from this plugin for PR metadata and patch context, but treat thread-aware review data as a `gh api graphql` problem because the connector comment surface is flat and does not preserve full review-thread state. Run all `gh` commands with elevated network access. If CLI auth is required, confirm `gh auth status` first and ask the user to authenticate with `gh auth login` if it fails. ## Workflow 1. Resolve the PR. - If the user provides a repository and PR number or URL, use that directly. - If the request is about the current branch PR, use local git context plus `gh auth status` and `gh pr view --json number,url` to resolve it. 2. Inspect review context with thread-aware reads. - Use the GitHub app from this plugin to fetch PR metadata and patch context when the repo and PR are known. - Use the bundled `scripts/fetch_comments.py` workflow whenever the task depends on unresolved review threads, inline review locations, or resolution state. That script fetches `reviewThreads`, `isResolved`, `isOutdated`, and file and line anchors that the connector comment surface does not preserve. - Use connector-only comment reads only for lightweight top-level PR comment summaries. 3. Cluster actionable review threads. - Group comments by file or behavior area. - Separate actionable change requests from informational comments