pr-threads-resolve
pr-threads-resolve automates the bulk marking of PR review threads as resolved on the current branch's pull request, typically after manual fixes or automated addressing via /pr-threads-address. It fetches unresolved threads, displays their details including file locations and comment text, requests confirmation, resolves selected threads, and provides a summary of completed resolutions using the gh pr-review extension.
git clone --depth 1 https://github.com/posit-dev/skills /tmp/pr-threads-resolve && cp -r /tmp/pr-threads-resolve/github/pr-threads-resolve ~/.claude/skills/pr-threads-resolveSKILL.md
## Prerequisites
### gh pr-review extension
Before using this command, check if the gh pr-review extension is installed:
```bash
gh extension list | grep -q pr-review || gh extension install agynio/gh-pr-review
```
### Resolve PR context first
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:
```bash
gh pr view --json number -q .number
```
Get the repository slug:
```bash
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).
## Workflow
1. Fetch and display all unresolved PR review threads
2. Show thread details (file, line, comment text)
3. Ask for confirmation or allow selective resolution
4. Resolve the confirmed threads
5. Report back with a summary of resolved threads
## CLI Reference
### List Review Threads
```bash
gh pr-review threads list --pr <number> --repo <owner/repo>
```
Filter with `--unresolved` or `--resolved`.
### Resolve / Unresolve Threads
```bash
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>
```
### Bulk Resolve Example
Substitute the actual PR number and repo slug resolved in "Resolve PR context first" — the `42` / `owner/repo` below are placeholders.
```bash
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
```>
Create and use brand.yml files for consistent branding across Shiny apps and Quarto documents. Covers: (1) Creating new _brand.yml files, (2) Applying to Shiny (R and Python), (3) Using in Quarto, (4) Modifying existing files, and (5) Troubleshooting. Includes complete specifications and integration guides.
Write ggsql queries — a grammar of graphics for SQL. Use when the user wants to create, modify, or understand a ggsql visualization query.
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Activate when the user says "create pr", "make a pr", "open pull request", "submit pr", "pr for these changes", or wants to get their current work into a reviewable PR. Assumes the project uses git, is hosted on GitHub, and has GitHub Actions CI with automated checks (lint, build, tests, etc.). Does NOT merge - stops when CI passes and provides the PR link.
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.
>
Guide for drafting issue closure and decline responses as an open-source package maintainer. Use when helping compose a reply that says \"no\" to a feature request, closes an issue as won't-fix, redirects a user to a different package, explains why a design choice is intentional, or otherwise declines or closes a community contribution. Also use when the maintainer needs to explain a deprecation, point out a user misunderstanding, or communicate an effort/scope tradeoff to a contributor.
>