How do I install the Pr Threads Address skill?

Run npx skillmds add posit-dev/pr-threads-address in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pr Threads Address safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pr Threads Address?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pr Threads Address free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Pr Threads Address?

posit-dev (@posit-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pr Threads Address by posit-dev — Agent Skill

Name: Pr Threads Address
Rating: 4.2 (5 reviews)
Author: posit-dev

Pr Threads Address

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.

posit-dev b093c4a 2.7 KB Updated Sep 9, 2026

File contents

Prerequisites

gh pr-review extension

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

Resolve PR context

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 (review view, comments reply, threads resolve, etc.).

Workflow

Fetch and display all unresolved PR review threads
Analyze each thread to understand the requested changes
For each thread:
1. Make the necessary code modifications
2. (When possible) Add unit tests to verify the change
3. 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.

CLI 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> — Comma-separated review states (APPROVED, CHANGES_REQUESTED, COMMENTED, DISMISSED)
--unresolved — Show only unresolved threads
--tail <n> — Show only the last n replies per thread
--include-comment-node-id — Include GraphQL node IDs for replies

Reply to Review Threads

gh pr-review comments reply --thread-id <PRRT_...> --body "<reply-text>" --repo <owner/repo> --pr <number>

For multi-line replies, pass --body "$(cat <<'EOF' ... EOF\n)" heredoc syntax.

Resolve a Thread

gh pr-review threads resolve --thread-id <PRRT_...> --pr <number> --repo <owner/repo>

Thread IDs (format PRRT_...) come from review view --include-comment-node-id.

---name: pr-threads-addressdescription: 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.license: MIT--- ## 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 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 (review view, comments reply, threads resolve, etc.). ## Workflow 1. Fetch and display all unresolved PR review threads 2. Analyze each thread to understand the requested changes 3. For each thread: 1. Make the necessary code modifications 2. (When possible) Add unit tests to verify the change 3. Commit the changes with descriptive commit messages using conventional commit specification 4. Report back with a summary of addressed threads 5. Ask if the user wants to resolve the threads. If so, reply to each thread indicating what was done and then resolve the thread. ## CLI Reference ### View PR Reviews and Comments Display all reviews, inline comments, and replies for a pull request: ```bash gh pr-review review view --pr <number> --repo <owner/repo> ``` **Common filters:** - `--reviewer <login>` — Filter by specific reviewer - `--states <list>` — Comma-separated review states (APPROVED, CHANGES_REQUESTED, COMMENTED, DISMISSED) - `--unresolved` — Show only unresolved threads - `--tail <n>` — Show only the last n replies per thread - `--include-comment-node-id` — Include GraphQL node IDs for replies ### Reply to Review Threads ```bash gh pr-review comments reply --thread-id <PRRT_...> --body "<reply-text>" --repo <owner/repo> --pr <number> ``` For multi-line replies, pass `--body "$(cat <<'EOF' ... EOF\n)"` heredoc syntax. ### Resolve a Thread ```bash gh pr-review threads resolve --thread-id <PRRT_...> --pr <number> --repo <owner/repo> ``` Thread IDs (format `PRRT_...`) come from `review view --include-comment-node-id`.

Frequently asked questions