address-pr-comments

address-pr-comments is a skill for Claude Code from tommyvo/useful-prompts. It costs 73 tokens per session (953 once invoked), scanned A, original, Unlicense.

A skill for finding unresolved comments on a GitHub pull request and handling them one by one. It can change the code when appropriate, or draft a reply for approval when a code change is not suitable.

In plain words
What is it for?
Reading unresolved review threads, fixing the related code, preparing responses that need approval, and resolving addressed threads.
Why use it?
It prevents review feedback from being missed and keeps the pull request's discussion and resolution status up to date.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Good fit Reading unresolved review threads, fixing the related code, preparing responses that need approval, and resolving addressed threads.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tommyvo/useful-prompts/address-pr-comments
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add tommyvo/useful-prompts --skill address-pr-comments
Clone the repo
git clone --depth 1 https://github.com/tommyvo/useful-prompts

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for address-pr-comments

README.md
[![agentmods](https://agentmods.dev/badge/skills/tommyvo/useful-prompts/address-pr-comments/github.svg)](https://agentmods.dev/skills/tommyvo/useful-prompts/address-pr-comments)
Your own site
<a href="https://agentmods.dev/skills/tommyvo/useful-prompts/address-pr-comments"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/address-pr-comments/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for address-pr-comments

Your own site · 80×15
<a href="https://agentmods.dev/skills/tommyvo/useful-prompts/address-pr-comments"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/address-pr-comments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 953 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00073 $0.00953
Opus 5.5 $0.00029 $0.00381
Sonnet 5.5 $0.00015 $0.00191
Haiku 4.5 $0.00007 $0.00095

Measured 2d ago against content hash 7ba7f674438b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

address-pr-comments scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Claude Code/Skills/address-pr-comments/SKILL.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Address PR Comments

Use ONLY the gh CLI for every GitHub operation in this skill (fetching, replying, resolving). Do not use any GitHub MCP server or editor GitHub extension tools: they can't see private repos that gh can.

Step 1: Identify the PR

  • If a PR number/URL is given, use it. Otherwise resolve the current branch's PR:
gh pr view --json number,title,url

Step 2: Fetch unresolved review threads

The REST API (gh api repos/{owner}/{repo}/pulls/{number}/comments) does not expose resolution state — use the GraphQL API instead:

gh api graphql -f query='
query {
  repository(owner: "<owner>", name: "<repo>") {
    pullRequest(number: <number>) {
      reviewThreads(first: 100) {
        nodes {
          id
          isResolved
          path
          line
          comments(first: 20) {
            nodes { id databaseId author { login } body path diffHunk }
          }
        }
      }
    }
  }
}
'

Filter to isResolved: false nodes. Each thread's id (e.g. PRRT_...) is needed to resolve it later; each comment's databaseId is needed to reply to it. If there are many threads, save the JSON to a temp file and read it rather than parsing inline.

Step 3: Address each unresolved thread

For every unresolved thread, read the file/line referenced and understand the reviewer's concern before touching anything — some bots (e.g. optibot) restate stale line numbers after later commits shift the diff, so verify against the current file contents, not just the diff hunk.

Then decide, per thread:

  • Fix it — the concern is valid and in-scope. Make the minimal code change that addresses it. Update/add specs covering the change. Prefer matching existing patterns in the surrounding code over inventing new ones.
  • Comment instead — the concern is a false positive, out of scope, a deliberate tradeoff, or you disagree. Draft a short reply explaining why, but do not post it yet — see Step 5.

Don't batch unrelated fixes into one giant diff-reading pass; address threads one at a time so each fix can be tied back to its thread.

Read the full file on GitHub · 110 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago Changed · +2 lines 7ba7f674438b
  2. 2mo ago First seen · 108 lines · 73 tokens per session scan A 844fa8c7b90a

Subscribe to this mod's changes

address-pr-comments is a skill published in the GitHub repository tommyvo/useful-prompts (4 stars, last pushed 2d ago), licensed Unlicense. It adds 73 tokens to every session and 953 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

Yeachan-Heo/oh-my-claudecode · 47 tokens

merge-batch

Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.

diegosouzapw/OmniRoute · 46 tokens

otto-pr-review-loop

Run Polly and OCR on a PR until all findings settle.

omnigent-ai/omnigent · 17 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

github-contributor

A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.

daymade/claude-code-skills · 105 tokens

revdiff

Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…

umputun/revdiff · 248 tokens