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.
>
>
>
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
>-
Research a codebase and create architectural documentation describing how features or systems work. Use when the user asks to: (1) Document how a feature works, (2) Create an architecture overview, (3) Explain code structure for onboarding or knowledge transfer, (4) Research and describe a system's design. Produces markdown documents with Mermaid diagrams and stable code references suitable for humans and AI agents.