What is handle-pr-comment?

A workflow for handling a comment on a GitHub pull request, including checking the code and deciding whether to make the requested change. A pull request is a proposed code change submitted for review before it is merged.

Use it to inspect PR comments, implement approved fixes when appropriate, or draft an explanation for changes that should not be made.

It helps distinguish actionable review feedback from questions or objections and keeps the response grounded in the current code and discussion.

handle-pr-comment — 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-comment

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

Your own site

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

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

When invoked 952 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.00030	$0.00952
Opus 5.5	$0.00012	$0.00381
Sonnet 5.5	$0.00006	$0.00190
Haiku 4.5	$0.00003	$0.00095

Measured 22d ago against content hash f4edea7916f6, 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-comment 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-comment/SKILL.md · 113 lines

How it starts

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

Handle PR Comment

Evaluates a comment on a GitHub pull request and responds appropriately, either implementing the requested change or drafting a reply explaining why the change will not be made. On user approval it commits and pushes code changes; whether the reply comment is posted to GitHub is decided by should-post-to-github (based on ~/.sdlc/config.yaml), otherwise the drafted reply is shown without posting.

Prerequisites

gh CLI authenticated with write access to the target repository
PR URL ($1) pointing to an open pull request
Git push access to the PR branch

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-comment.

Communication guidelines (outbound text)

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

Workflow

Fetch PR metadata + comment history
            |
            v
      Clone repository
            |
            v
   Is the comment actionable?
         /          \
       Yes            No
        |              |
        v              v
  Implement       Draft rejection
  changes         explanation
        |              |
        +------+--------+
               |
               v
   Present to user for approval
       /          \
   Approved      Rejected
      |              |
      v              v
  Commit +       Skip
  push
  (always on approval);
  post reply only if
  should-post-to-github allows

Steps

Fetch PR details and full comment history:
```
gh pr view $1 --comments
```
Clone the repository locally:
```
gh repo clone <owner>/<repo>
```
Display the target comment's content.
Evaluate whether the feedback is appropriate and actionable.
If actionable: implement the changes in the codebase.
If not actionable: draft a reply explaining the rejection.
Present reasoning to the user for approval.
On approval:
- For code changes: commit and push to the PR branch (push is not gated).
- For posting a reply comment: get the PR author (gh pr view $1 --json author --jq .author.login), then run ~/.agents/scripts/should-post-to-github --repo "<owner>/<repo>" --author "<PR_AUTHOR>". If it exits 0, post the reply via gh with the Skill attribution footer on the comment body. If it exits 1, present the drafted reply to the user without posting.

Read the full file on GitHub · 113 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 · +4 lines f4edea7916f6
27d ago Changed d14cddaae405
28d ago Changed · +4 lines f5d38cce0fb3
1mo ago First seen · 105 lines · 30 tokens per session scan A 07122767d6e1

Subscribe to this mod's changes

handle-pr-comment is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 952 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-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