review-pr

review-pr is a skill for Claude Code from pronskiy/php-src-developer. It costs 124 tokens per session (2,121 once invoked), scanned C, original, MIT.

A review workflow for checking a GitHub pull request, a proposed change to a project, and writing findings to REVIEW.md.

In plain words
What is it for?
Use it to review php-src or another GitHub pull request and, after confirmation, post findings as inline comments with the GitHub command-line tool.
Why use it?
It organizes code-review findings against PHP project standards while keeping publication of comments under your control.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the php-core-developer plugin — 9 skills, 1 agent shipped together

Good fit Use it to review php-src or another GitHub pull request and, after confirmation, post findings as inline comments with the GitHub command-line tool.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pronskiy/php-src-developer/review-pr
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 pronskiy/php-src-developer --skill review-pr
Clone the repo
git clone --depth 1 https://github.com/pronskiy/php-src-developer

Made for: Claude Code.

Or install php-core-developer, the plugin that ships this one along with the rest of its 9 skills, 1 agent.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/pronskiy/php-src-developer/review-pr/github.svg)](https://agentmods.dev/skills/pronskiy/php-src-developer/review-pr)
Your own site
<a href="https://agentmods.dev/skills/pronskiy/php-src-developer/review-pr"><img src="https://agentmods.dev/badge/skills/pronskiy/php-src-developer/review-pr/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 review-pr

Your own site · 80×15
<a href="https://agentmods.dev/skills/pronskiy/php-src-developer/review-pr"><img src="https://agentmods.dev/badge/skills/pronskiy/php-src-developer/review-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,121 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00124 $0.02121
Opus 5.5 $0.00050 $0.00848
Sonnet 5.5 $0.00025 $0.00424
Haiku 4.5 $0.00012 $0.00212

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

Security

Grade C, and why

review-pr scanned grade C with 1 finding 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 1mo 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.

Tells the agent never to refusehighAnti-refusal

Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.

| Author is the user themselves | Still review. Many php-src contributors review their own PRs before requesting feedback on internals@. Don't refuse. |
plugins/php-core-developer/skills/review-pr/SKILL.md · 187 lines

How it starts

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

review-pr

Review a GitHub pull request against php-src coding standards. Produces REVIEW.md in pwd. Optionally posts findings as inline review comments via the gh CLI — only on explicit user confirmation.

Inputs

  1. PR identifier (required) — a number (12345), #12345, or URL (https://github.com/php/php-src/pull/12345). Default repo is php/php-src.
  2. gh CLI — must be authenticated (gh auth status).
  3. $PHP_SRC_DIR — used to read surrounding context for the diff (file content beyond the hunk).

What it produces

  • REVIEW.md in the task directory resolved per _shared/task-dir.md (default $PHP_SRC_DIR/.claude/php-core-dev/pr-<N>/REVIEW.md) — severity-graded findings, same format as review-local.
  • Slug: pr-<N>. Written to .current.
  • Optionally, on user "yes": inline review comments on the PR via gh pr review / gh api.

Workflow

1. Pre-checks

  • gh auth status succeeds. Otherwise stop with Run: gh auth login.
  • $PHP_SRC_DIR is set and looks like php-src.
  • Argument resolves to a PR.

2. Fetch PR metadata + diff

gh pr view <PR-N> --repo php/php-src \
  --json number,title,body,state,baseRefName,headRefName,headRefOid,url,files,author,labels

gh pr diff <PR-N> --repo php/php-src

Record:

  • Title, author, base branch, head branch (baseRefName / headRefName)
  • Head SHA (headRefOid) — needed for posting inline comments
  • File list with status (added / modified / removed / renamed)
  • Total additions / deletions
  • PR URL

If the PR is closed or merged, proceed but note it in the Scope section.

3. Backup existing REVIEW.md

test -f ./REVIEW.md && mv ./REVIEW.md ./REVIEW.md.bak

4. Read surrounding context

For each touched file, read the post-image from $PHP_SRC_DIR if the PR is against the same checked-out branch as the working tree. Otherwise, read via gh:

gh api /repos/php/php-src/contents/<path>?ref=<headRefOid> --jq '.content' | base64 -d

Read the full file on GitHub · 187 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. 1mo ago First seen · 187 lines · 124 tokens per session scan C 0d3a432d6f83

Subscribe to this mod's changes

review-pr is a skill published in the GitHub repository pronskiy/php-src-developer (8 stars, last pushed 4mo ago), licensed MIT. It adds 124 tokens to every session and 2,121 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens