posit-dev/pr-threads-resolve
Bulk resolve unresolved PR review threads on the current branch’s PR — typically after threads have been addressed manually or via /pr-threads-address
npx skills add https://github.com/posit-dev/skills --skill pr-threads-resolve
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 (list, resolve, view, reply).
gh pr-review threads list --pr <number> --repo <owner/repo>
Filter with --unresolved or --resolved.
gh pr-review threads resolve --thread-id <PRRT_...> --pr <number> --repo <owner/repo>
gh pr-review threads unresolve --thread-id <PRRT_...> --pr <number> --repo <owner/repo>
Substitute the actual PR number and repo slug resolved in "Resolve PR context first" — the 42 / owner/repo below are placeholders.
gh pr-review threads list --pr 42 --unresolved --repo owner/repo | \
jq -r '.threads[].id' | \
xargs -I {} gh pr-review threads resolve --thread-id {} --pr 42 --repo owner/repo
Take posit-dev/pr-threads-resolve from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.