respond-to-pr-comments-in-blocklistlisted

# Respond to PR comments in blocklist Use this skill to respond to PR comments on the current branch. If comments are already visible in the conversation, typically from the built-in `/pr-comments` skill, continue from that context. If comments are not already visible, fetch and display them first, then guide the user through each actionable comment, collect an explicit decision, make requested code changes, and only then ask for approval before posting GitHub replies or resolving review threads. ## When not to use this skill Skip this skill when the user only wants PR comments fetched or displayed (use `pr-comments` instead) or only wants the underlying code changes made, with no intent to post replies or resolve threads on GitHub. Read this skill only once the user has confirmed they want replies posted or threads resolved. ## Preconditions - Work in the repository checkout for the PR branch. - Do not refetch comments unless the loaded context is missing essential fields such as comment body, author, URL, path, or line metadata. - Do not post GitHub replies, submit reviews, or resolve threads until the final preview is approved by the user. If no PR comments are present in context, fetch and display them before continuing. Prefer invoking the built-in `/pr-comments` workflow when available. Otherwise use the equivalent GitHub CLI fallback: identify the current PR, fetch PR-level comments, review comments, and review bodies, then display them with `insert_code_review_c