- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add posit-dev/skills --skill pr-threads-address -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add posit-dev/skills --skill pr-threads-address -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add posit-dev/skills --skill pr-threads-address -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add posit-dev/skills --skill pr-threads-address -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/posit-dev/skills/tree/HEAD/github/pr-threads-addressFrom the publisher
Before using this command, check if the gh pr-review extension is installed:
gh extension list | grep -q pr-review || gh extension install agynio/gh-pr-review
Every gh pr-review subcommand requires both --pr <number> and --repo <owner/repo> — do not omit either. Look the values up once at the start of the workflow and substitute the literal numbers and slugs into every later command.
Get the PR number for the current branch:
gh pr view --json number -q .number
Get the repository slug:
gh repo view --json nameWithOwner -q .nameWithOwner
Then pass the resulting values directly — e.g. --pr 42 --repo posit-dev/skills — on every subsequent gh pr-review call in this workflow (review view, comments reply, threads resolve, etc.).
Display all reviews, inline comments, and replies for a pull request:
gh pr-review review view --pr <number> --repo <owner/repo>
Common filters:
--reviewer <login> — Filter by specific reviewer--states <list> — Comma-separated review states (APPROVED, CHANGES_REQUESTED, COMMENTED, DISMISSED)--unresolved — Show only unresolved threads--tail <n> — Show only the last n replies per thread--include-comment-node-id — Include GraphQL node IDs for repliesgh pr-review comments reply --thread-id <PRRT_...> --body "<reply-text>" --repo <owner/repo> --pr <number>
For multi-line replies, pass --body "$(cat <<'EOF' ... EOF\n)" heredoc syntax.
gh pr-review threads resolve --thread-id <PRRT_...> --pr <number> --repo <owner/repo>
Thread IDs (format PRRT_...) come from review view --include-comment-node-id.
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where usef
---name: pr-threads-addressdescription: Address PR review feedback by systematically working through every unresolved PR review thread on the current…---# github/pr-threads-address/SKILL.mdOverview
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
FAQ
Download github/pr-threads-address/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/posit-dev/skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.