pr-threads-resolve
Skill2 starsChanged 6 months agoMITView on GitHub
Bulk resolve unresolved PR review threads. Useful after manually addressing threads or after using /pr-threads-address.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- BrightGold70/skillsword for word, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- BrightGold70/skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- alt-textSkill
- brand-ymlSkill
- cliSkill
- cran-extrachecksSkill
- create-release-checklistSkill
- critical-code-reviewerSkill
- describe-designSkill
- ggsqlSkill
- implementSkill
- maintainer-declineSkill
- miraiSkill
- pr-createSkill
- pr-threads-addressSkill
- quarto-authoringSkill
- r-cli-appSkill
- release-postSkill
- review-testingSkill
- r-package-developmentSkill
- shiny-bslibSkill
- shiny-bslib-themingSkill
- testing-r-packagesSkill
- working-onSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Note: If PR_NUMBER is omitted, the command will automatically detect and use the PR associated with the current branch.
- Distinctive: line 23
Ask for confirmation or allow selective resolution
- Distinctive: line 29
Use this command when you have already addressed PR review threads and want to bulk resolve them, or when you need to clean up threads that …
- Distinctive: line 40
Ask which threads to resolve (all or specific ones)
- Distinctive: line 46
Before using this command, check if the gh pr-review extension is installed:
- Very specific: line 107
Repository Context: Always include --repo owner/repo to ensure correct repository context, or run commands from within a local clone of the …
- Very specific: line 111
State Filters: When using --states, provide a comma-separated list: --states APPROVED,CHANGES_REQUESTED
- Very specific: line 113
Unresolved Focus: Use --unresolved --not_outdated together to focus on actionable comments that need attention.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/pr-threads-resolve
Usage: /pr-threads-resolve [PR_NUMBER]
Description: Bulk resolve unresolved PR review threads. Useful after manually addressing threads or after using /pr-threads-address.
Note: If PR_NUMBER is omitted, the command will automatically detect and use the PR associated with the current branch.
Workflow
- Fetch and display all unresolved PR review threads
- Show thread details (file, line, comment text)
- Ask for confirmation or allow selective resolution
- Resolve the confirmed threads
- Report back with a summary of resolved threads
When to use
Use this command when you have already addressed PR review threads and want to bulk resolve them, or when you need to clean up threads that are no longer relevant.
Example
/pr-threads-resolve 42This will:
- List all unresolved threads on PR #42
- Show what each thread is about
- Ask which threads to resolve (all or specific ones)
- Resolve the selected threads
- Provide a summary of resolved items
Prerequisites
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-reviewCLI Reference
List Review Threads
Enumerate all review threads with filtering:
gh pr-review threads list --pr <number> --repo <owner/repo>Common filters:
--unresolved— Show only unresolved threads--resolved— Show only resolved threads
View PR Reviews and Comments
Display reviews, inline comments, and replies with full context:
gh pr-review review view --pr <number> --repo <owner/repo>Common filters:
--reviewer <login>— Filter by specific reviewer--states <list>— Filter by review state (APPROVED, CHANGES_REQUESTED, COMMENTED, DISMISSED)--unresolved— Show only unresolved threads--not_outdated— Exclude outdated threads--tail <n>— Show only the last n replies per thread--include-comment-node-id— Include GraphQL node IDs for replies
Resolve / Unresolve Threads
Toggle thread resolution status:
# Resolve a thread
gh pr-review threads resolve --thread-id <PRRT_...> --pr <number> --repo <owner/repo>
# Unresolve a thread
gh pr-review threads unresolve --thread-id <PRRT_...> --pr <number> --repo <owner/repo>Bulk Resolve Example
# Get all unresolved thread IDs and resolve them
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/repoUsage Notes
- Repository Context: Always include
--repo owner/repoto ensure correct repository context, or run commands from within a local clone of the repository. - Thread IDs: Thread IDs (format
PRRT_...) can be obtained fromreview view --include-comment-node-idorthreads listcommands. - State Filters: When using
--states, provide a comma-separated list:--states APPROVED,CHANGES_REQUESTED - Unresolved Focus: Use
--unresolved --not_outdatedtogether to focus on actionable comments that need attention.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

