What is pr-review-send?

A workflow for writing review comments on specific files and line numbers in a GitHub pull request. Pull requests are proposed code changes submitted for review before merging.

Use it to compose and post individual GitHub pull-request comments tied to exact code locations.

It removes the manual work of formatting and sending line-level review feedback, while allowing comments to be reviewed before they are posted when sending is disabled.

pr-review-send — Skill for Claude Code by tomzx

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 pr-review-send

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

Your own site

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

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

When invoked 729 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.00022	$0.00729
Opus 5	$0.00011	$0.00365
Sonnet 5	$0.00004	$0.00146
Haiku 4.5	$0.00002	$0.00073

Measured 6d ago against content hash f1458b261b81, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

pr-review-send 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 6d 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/pr-review-send/SKILL.md · 66 lines

How it starts

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

Send PR Review Comments

Posts individual PR review comments to GitHub by file and line number using the pr-comment.py script from the personal-automation repository. Whether the comments are actually sent to GitHub is decided by should-post-to-github (based on ~/.sdlc/config.yaml); when posting is disabled the comments are composed and shown for review instead.

Prerequisites

uv installed
pr-comment.py script at $HOME/repos/git/personal-automation/others/pr-comment.py
GitHub authentication configured for the script
Must run from within $HOME/repos/git/personal-automation

Skill attribution (GitHub)

Before each pr-comment.py invocation, read github-post-attribution/SKILL.md and append the Posted with footer for SKILL_DIR = pr-review-send to the --comment text.

Steps

Navigate to the automation directory:
```
cd $HOME/repos/git/personal-automation
```
Compose each review comment (including the Skill attribution footer).
Decide whether to post: get the PR author with gh pr view <pr-number> --repo <owner>/<repo> --json author --jq .author.login, then run ~/.agents/scripts/should-post-to-github --repo "<owner>/<repo>" --author "<PR_AUTHOR>". If it exits 1, present the comments to the user and stop without posting.

If it exits 0, post a review comment (--comment includes main text plus Skill attribution footer):

uv run $HOME/repos/git/personal-automation/others/pr-comment.py <owner>/<repo> <pr-number> \
  --file <path/to/file.py> \
  --line <line-number> \
  --comment "<comment text>"

Repeat for each additional comment on different files or lines.

Example Usage

Scenario 1: Comment on a specific line

/pr-review-send owner/myrepo 123 \
  --file src/main.py \
  --line 42 \
  --comment "This function should handle the case where input is None."

Posts the comment to PR #123 on src/main.py line 42, unless should-post-to-github excludes the repo or author (in which case the comment is composed and shown without posting).

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

6d ago First seen · 66 lines · 22 tokens per session scan A f1458b261b81

Subscribe to this mod's changes

pr-review-send is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 729 once invoked, about $0.0001 per session on Opus 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 Commits Git and workflow

review-implement-phase

Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.

prisma/orm · 38 tokens

github-pr-workflow

Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.

paperclipai/paperclip · 39 tokens

work-unit-commits

Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.

Gentleman-Programming/gentle-ai · 33 tokens

review-delta

Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.

tirth8205/code-review-graph · 24 tokens

github-contributor

End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…

daymade/claude-code-skills · 133 tokens

pr-pending-feedback

Evaluate pending (unsubmitted) review comments on the current branch's PR and, after user confirmation, address each in a separate sub-agent and separate commit.

ryanb/dotfiles · 36 tokens