‹ 首页

pr-threads-address

@posit-dev · 收录于 1 周前

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.

场景代码评审pr跟进修改反馈

适合你，如果经常收到 PR 评审意见需要逐条修改并回复

/ 下载安装
pr-threads-address.skill双击,或拖进 Claude 桌面版 / Cowork,即完成安装↓ .skill↓ .zip
用别的 agent?下载 .zip 解压,把文件夹放进它的技能目录
Claude Code~/.claude/skills/(项目级 .claude/skills/)
Codex CLI~/.codex/skills/
Cursor自动读取上面两处目录
其他工具见其文档的「skills」目录;两个下载是同一份文件,只是名字不同
/ 通过 npx 安装 校验哈希
npx oh-my-skill add posit-dev/skills/pr-threads-address
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- posit-dev/skills/pr-threads-address
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify posit-dev/skills/pr-threads-address
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
424GitHub stars
~624上下文体积 · 单文件
镜像托管

怎么用

技能原文 SKILL.md作者撰写 · MIT · 3c7bf42
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
  1. Fetch and display all unresolved PR review threads
  2. Analyze each thread to understand the requested changes
  3. For each thread:
  4. Make the necessary code modifications
  5. (When possible) Add unit tests to verify the change
  6. Commit the changes with descriptive commit messages using conventional commit specification
  7. Report back with a summary of addressed threads
  8. 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.

按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…