pr-addr-feedback

pr-addr-feedback is a command for Claude Code from a8cteam51/claude-code-plugins. It costs 47 tokens per session (927 once invoked), scanned A, original, MIT.

A command for addressing unresolved, non-outdated review comments on a GitHub pull request. A pull request is a proposed code change awaiting review.

In plain words
What is it for?
Use it with a GitHub pull-request URL to inspect unresolved comments, summarize them, and address the requested changes.
Why use it?
It gathers the remaining review threads and guides work on them, including for private repositories authenticated through the GitHub command-line tool.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Good fit Use it with a GitHub pull-request URL to inspect unresolved comments, summarize them, and address the requested changes.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/a8cteam51/claude-code-plugins/pr-addr-feedback
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.

Clone the repo
git clone --depth 1 https://github.com/a8cteam51/claude-code-plugins

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 pr-addr-feedback

README.md
[![agentmods](https://agentmods.dev/badge/commands/a8cteam51/claude-code-plugins/pr-addr-feedback/github.svg)](https://agentmods.dev/commands/a8cteam51/claude-code-plugins/pr-addr-feedback)
Your own site
<a href="https://agentmods.dev/commands/a8cteam51/claude-code-plugins/pr-addr-feedback"><img src="https://agentmods.dev/badge/commands/a8cteam51/claude-code-plugins/pr-addr-feedback/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 pr-addr-feedback

Your own site · 80×15
<a href="https://agentmods.dev/commands/a8cteam51/claude-code-plugins/pr-addr-feedback"><img src="https://agentmods.dev/badge/commands/a8cteam51/claude-code-plugins/pr-addr-feedback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 927 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.00047 $0.00927
Opus 5.5 $0.00019 $0.00371
Sonnet 5.5 $0.00009 $0.00185
Haiku 4.5 $0.00005 $0.00093

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

Security

Grade A, and why

pr-addr-feedback 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 2mo 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.

plugins/pr-feedback/commands/pr-addr-feedback.md · 111 lines

How it starts

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

You are helping the user address unresolved review comments on a GitHub pull request. The PR URL is: $ARGUMENTS

Step 1: Parse the PR URL

Extract owner, repo, and pull_number from the URL. The URL format is: https://github.com/{owner}/{repo}/pull/{pull_number}

Step 2: Fetch unresolved review threads

Use the GitHub GraphQL API via gh api graphql to fetch all unresolved threads and their comments:

gh api graphql -f query='
{
  repository(owner: "OWNER", name: "REPO") {
    pullRequest(number: PULL_NUMBER) {
      title
      headRefName
      reviewThreads(first: 100) {
        nodes {
          id
          isResolved
          isOutdated
          comments(first: 10) {
            nodes {
              body
              path
              line
              originalLine
              diffHunk
              author { login }
              url
              createdAt
            }
          }
        }
      }
    }
  }
}'

Filter to threads where isResolved is false and isOutdated is false. If there are no unresolved threads, tell the user and stop.

Step 3: Show a summary

Before doing anything, print a brief summary:

  • PR title and branch
  • Number of unresolved threads found
  • List of files touched by comments

Then proceed without asking for confirmation.

Step 4: Process each thread

For each unresolved thread, work through the following logic. Process them one at a time, in order.

4a: Read context

Use the Read tool to open the file at path. Focus on the lines referenced in line or originalLine, plus ~15 lines of surrounding context.

Also look at diffHunk from the comment — it shows the exact diff context the reviewer saw.

4b: Evaluate validity

Assess whether the feedback is valid. Consider:

  • Is the suggested change technically correct?
  • Does it improve clarity, correctness, performance, or security?
  • Is it a matter of style/preference with no clear right answer?
  • Does the comment contradict the existing codebase patterns?
  • Is the comment outdated (e.g., refers to code that no longer exists)?

Read the full file on GitHub · 111 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. 2mo ago First seen · 111 lines · 47 tokens per session scan A f3e1d7c70cd6

Subscribe to this mod's changes

pr-addr-feedback is a command published in the GitHub repository a8cteam51/claude-code-plugins (6 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 927 once invoked, about $0.0002 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

pr-addr-feedback compared with commands from other repositories

pr-addr-feedback next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
pr-addr-feedbacka8cteam51/claude-code-pluginsCommand6todayMITA47Claude Code
speckit.spex.submitrhuss/cc-spexCommand1223d agoApache-2.0A15Claude Code
merge-conflict-analysisrjmurillo/ai-agentsCommand49yesterdayMITA0GitHub Copilot
gitazrtydxb/procoderCommand21111d agoApache-2.0A20Claude Code
factoryfelvieira/claude-skills-fvCommand282d agoApache-2.0A47Claude Code
repo-audittractorjuice/arc-kitCommand2.3k2d agononeA29Claude Code
advanced-code-review-contextaxiomantic/spellbookCommand113d agoMITA19Claude Code