What is implement-pr-feedback?

A workflow for handling pull-request feedback, where reviewers comment on proposed code changes before they are merged.

Use it to inspect review threads, implement appropriate changes, reply to comments, and resolve completed threads.

It gathers the comments and tracks replies and resolutions, reducing the chance that review requests are missed.

How jnarowski/agentcmd configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to jnarowski/agentcmd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/jnarowski/agentcmd/main/.claude/commands/implement-pr-feedback.md

Clone the repo

git clone --depth 1 https://github.com/jnarowski/agentcmd

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/jnarowski/agentcmd/implement-pr-feedback/github.svg)](https://agentmods.dev/commands/jnarowski/agentcmd/implement-pr-feedback)

Your own site

<a href="https://agentmods.dev/commands/jnarowski/agentcmd/implement-pr-feedback"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/implement-pr-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/jnarowski/agentcmd/implement-pr-feedback"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/implement-pr-feedback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,535 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.

Model	Per session	Once invoked
Fable 5.1	$0.00013	$0.01535
Opus 5.5	$0.00005	$0.00614
Sonnet 5.5	$0.00003	$0.00307
Haiku 4.5	$0.00001	$0.00153

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

Security

Grade A, and why

implement-pr-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.

.claude/commands/implement-pr-feedback.md · 223 lines

How it starts

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

Implement PR Feedback

Atomic operation: fetch PR comments → analyze → implement → commit → reply to each thread → auto-resolve.

Variables

$pr-number: $1 (optional) - PR number (defaults to current branch PR)

Instructions

CRITICAL:

NEVER skip git hooks (no --no-verify)
Use HEREDOC for commit message with Claude footer
Check if changes exist before committing
Reply to EACH comment thread individually BEFORE resolving
Skip resolve gracefully if permission denied
Don't implement outdated comments without user confirmation
NEVER run additional commands beyond git/gh operations
NEVER use TodoWrite or Task tools

Workflow

1. Detect PR Number and Repo Info

Run these commands in parallel:

# Get PR number if not provided
gh pr view --json number -q .number

# Get repo owner and name for GraphQL API
gh repo view --json owner,name -q '"\(.owner.login)/\(.name)"'

If no PR found and $pr-number not provided, stop with error: "No PR found for current branch. Please provide PR number."

2. Fetch PR Comments and Reviews

gh pr view $PR_NUMBER --json reviews,reviewThreads

This returns JSON with:

reviews: Array of review objects with state (APPROVED, CHANGES_REQUESTED, COMMENTED), body, author
reviewThreads: Array of thread objects with isResolved, isOutdated, comments (array with body, path, line, id, author)

3. Parse and Display Structured Analysis

Parse the JSON to extract actionable comments. Filter and classify:

Filter criteria (actionable comments):

isResolved === false
isOutdated === false
NOT just approval/LGTM comments

Priority classification (based on keywords in comment body):

High: Review state is CHANGES_REQUESTED, or body contains "must", "required", "blocking", "needs", "have to"
Medium: Body contains "should", "consider", "suggest", "recommend", "could you", "please"
Low: Body contains "?", "why", "how come", "curious"

Display structured analysis like this:

Read the full file on GitHub · 223 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.

2mo ago First seen · 223 lines · 13 tokens per session scan A 20d57fdce0aa

Subscribe to this mod's changes

implement-pr-feedback is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 10mo ago), licensed MIT. It adds 13 tokens to every session and 1,535 once invoked, about $0.0001 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-09-01.

Code review Commits Git and workflow

implement-pr-feedback next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
implement-pr-feedbackjnarowski/agentcmd	Command	18	10mo ago	MIT	A	13	Claude Code
elegant-code-reviewathola/claude-night-market	Command	348	yesterday	MIT	A	27	Claude Code
prp-commitFmarzochi/EGC	Command	68	yesterday	Apache-2.0	A	15	Claude Code
gsd:pr-branchkryptobaseddev/cleo	Command	160	yesterday	MIT	A	24	Claude Code
validate-pr-descriptionrjmurillo/ai-agents	Command	49	yesterday	MIT	A	22	Claude Code
gitazrtydxb/procoder	Command	211	11d ago	Apache-2.0	A	20	Claude Code
karpathy-checkricneves-ai/flowgrammers-skills	Command	117	1mo ago	MIT	A	0	Claude Code

agentcmd: Command for Claude Code