pr-threads-address
Skill2 starsChanged 6 months agoMITView on GitHub
Review all unresolved PR review threads, address them by making necessary code changes, and commit the changes appropriately.
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-resolveSkill
- quarto-authoringSkill
- r-cli-appSkill
- release-postSkill
- review-testingSkill
- r-package-developmentSkill
- shiny-bslibSkill
- shiny-bslib-themingSkill
- testing-r-packagesSkill
- working-onSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 9 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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 26
Commit the changes with descriptive commit messages using conventional commit specification
- Distinctive: line 28
Ask if the user wants to resolve the threads.
- Distinctive: line 32
Use this command when you have received PR review feedback and need to systematically address all unresolved threads before the PR can be …
- Distinctive: line 43
Create commits for the changes
- Distinctive: line 46
Ask if you want to resolve the threads
- Distinctive: line 50
Before using this command, check if the gh pr-review extension is installed:
- Distinctive: line 96
Multi-line replies: use heredoc syntax:
- Distinctive: line 118
Create a new pending review to add comments before submission:
- Distinctive: line 128
Add inline comments to a pending review:
- Very specific: line 157
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 163
State Filters: When using --states, provide a comma-separated list: --states APPROVED,CHANGES_REQUESTED
- Very specific: line 165
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 372,429 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-address
Usage: /pr-threads-address [PR_NUMBER]
Description: Review all unresolved PR review threads, address them by making necessary code changes, and commit the changes appropriately.
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
- Analyze each thread to understand the requested changes
- For each thread:
- Make the necessary code modifications
- (When possible) Add unit tests to verify the change
- Commit the changes with descriptive commit messages using conventional commit specification
- Report back with a summary of addressed threads
- Ask if the user wants to resolve the threads. If so, reply to each thread indicating what was done and then resolve the thread.
When to use
Use this command when you have received PR review feedback and need to systematically address all unresolved threads before the PR can be merged.
Example
/pr-threads-address 42This will:
- View unresolved threads on PR #42
- Make code changes to address each thread
- Create commits for the changes
- Reply to reviewers with explanations
- Provide a summary of all addressed items
- Ask if you want to resolve the threads
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
View PR Reviews and Comments
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>— 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
Examples:
# View all unresolved comments
gh pr-review review view --pr 42 --unresolved --repo owner/repo
# View comments from a specific reviewer
gh pr-review review view --pr 42 --reviewer username --repo owner/repo
# View only change requests, excluding outdated threads
gh pr-review review view --pr 42 --states CHANGES_REQUESTED --not_outdated --repo owner/repoReply to Review Threads
Respond to specific review comment threads:
gh pr-review comments reply --thread-id <PRRT_...> --body "<reply-text>" --repo <owner/repo> --pr <number>Multi-line replies use heredoc syntax:
gh pr-review comments reply --thread-id PRRT_xyz789 --body "$(cat <<'EOF'
Fixed in commit abc123.
The changes include:
- Updated function signature
- Added error handling
- Updated tests
EOF
)" --repo owner/repo --pr 42Resolve a Thread
gh pr-review threads resolve --thread-id <PRRT_...> --pr <number> --repo <owner/repo>Start a Pending Review
Create a new pending review to add comments before submission:
gh pr-review review --start --pr <number> --repo <owner/repo>This returns a review ID (format: PRR_...) needed for adding comments.
Add Review Comments
Add inline comments to a pending review:
gh pr-review review --add-comment --review-id <PRR_...> --path <file-path> --line <number> --body "<comment-text>" --repo <owner/repo>Flags:
--review-id— Review ID from--startcommand (required)--path— File path in the repository (required)--line— Line number for the comment (required)--body— Comment text (required)
Submit a Review
Finalize and submit a pending review:
gh pr-review review --submit --review-id <PRR_...> --event <EVENT_TYPE> --body "<summary>" --repo <owner/repo>Event types:
APPROVE— Approve the changesREQUEST_CHANGES— Request changes before mergingCOMMENT— Submit general feedback without explicit approval
Usage 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. - Review IDs: Review IDs (format
PRR_...) are returned by thereview --startcommand and must be used for adding comments to that review. - 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.

