What is handle-pr-author-feedback?

A reviewer-side workflow that checks whether new commits in a GitHub pull request address earlier review comments. It inspects the updated code, resolves fixed discussion threads, and replies to comments that remain incomplete or disputed.

Use it after an author updates a pull request to verify each review point and respond to partial, missing, or rejected fixes.

It prevents review comments from being marked done without checking the actual implementation and keeps unresolved feedback visible.

handle-pr-author-feedback — Skill for Claude Code by tomzx/agents

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 tomzx/agents --skill handle-pr-author-feedback

Clone the repo

git clone --depth 1 https://github.com/tomzx/agents

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/skills/tomzx/agents/handle-pr-author-feedback/github.svg)](https://agentmods.dev/skills/tomzx/agents/handle-pr-author-feedback)

Your own site

<a href="https://agentmods.dev/skills/tomzx/agents/handle-pr-author-feedback"><img src="https://agentmods.dev/badge/skills/tomzx/agents/handle-pr-author-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/skills/tomzx/agents/handle-pr-author-feedback"><img src="https://agentmods.dev/badge/skills/tomzx/agents/handle-pr-author-feedback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,925 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.00053	$0.01925
Opus 5.5	$0.00021	$0.00770
Sonnet 5.5	$0.00011	$0.00385
Haiku 4.5	$0.00005	$0.00193

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

Security

Grade A, and why

handle-pr-author-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 22d 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.

skills/handle-pr-author-feedback/SKILL.md · 174 lines

How it starts

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

Handle PR Author Feedback

As the reviewer of a GitHub pull request, verifies that the author's fixes actually address the review feedback left earlier. For each unresolved review thread, inspects the current code and diff to decide whether the comment is addressed, partially addressed, not addressed, or reasonably rejected, then resolves the fixed threads and replies on the rest. Whether replies are posted and threads resolved on GitHub is decided by should-post-to-github (based on ~/.sdlc/config.yaml), otherwise replies are drafted without posting.

This skill never modifies the PR's code. To implement fixes on your own PR, use handle-pr-reviewer-feedback instead.

Prerequisites

gh CLI authenticated with write access to the target repository
PR number identifying an open pull request where you left review comments
- If $1 is provided, use it directly
- If $1 is not provided, resolve the PR number with: ghx pr list --head $(git branch --show-current) --json | jq '.[0].number'

Skill attribution (GitHub)

Before posting any PR comment with gh, read github-post-attribution/SKILL.md and append the Posted with footer for SKILL_DIR = handle-pr-author-feedback.

Communication guidelines (outbound text)

Before composing any text posted or drafted on the user's behalf, apply communication-guidelines/SKILL.md.

Workflow

Fetch PR threads + metadata ($1)
        |
        v
Filter to unresolved threads
authored by current user
        |
        v
   For each thread
        |
        v
   Inspect current code + diff
   since the comment
        |
        v
   Verdict: addressed / partial /
   not addressed / rebuttal
        |
        v
Present verdicts to user for approval
       /         \
   Approved     Rejected
      |             |
      v             v
   Resolve +      Skip
   reply per thread
   (ghx + GraphQL),
   only if
   should-post-to-github
   allows
      |
      v
All threads resolved? --Yes--> Suggest /quick-pr-review
                              to re-approve

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

22d ago Changed · +10 lines d544eb6ffb43
24d ago Changed 4267aadf0f29
27d ago Changed · +1 lines 94935b97adcc
28d ago Changed · +4 lines d2b09cae50b4
1mo ago First seen · 159 lines · 53 tokens per session scan A 22584774b3f9

Subscribe to this mod's changes

handle-pr-author-feedback is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 1,925 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-09-03.

Code review Git and workflow

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