review-local

review-local is a skill for Claude Code from pronskiy/php-src-developer. It costs 102 tokens per session (1,722 once invoked), scanned A, original, MIT.

A read-only workflow that reviews changes in a local copy of php-src, the source code repository for PHP, and writes findings to REVIEW.md.

In plain words
What is it for?
Use it to inspect your current branch against the default branch or another chosen base and identify issues against PHP coding standards.
Why use it?
It gives you a structured check of your current code changes before you send them to others for review.

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 inspect your current branch against the default branch or another chosen base and identify issues against PHP coding standards.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pronskiy/php-src-developer/review-local
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-local
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-local

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/pronskiy/php-src-developer/review-local"><img src="https://agentmods.dev/badge/skills/pronskiy/php-src-developer/review-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,722 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00102 $0.01722
Opus 5.5 $0.00041 $0.00689
Sonnet 5.5 $0.00020 $0.00344
Haiku 4.5 $0.00010 $0.00172

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

Security

Grade A, and why

review-local 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 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.

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.

plugins/php-core-developer/skills/review-local/SKILL.md · 139 lines

How it starts

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

review-local

Review the user's current local php-src diff. Read-only. Produces REVIEW.md in pwd.

Inputs

  1. $PHP_SRC_DIR — the php-src checkout.
  2. Optional base ref — defaults to git merge-base HEAD origin/master. User can override (/review-local PHP-8.3).
  3. The skill operates against the current branch in $PHP_SRC_DIR. It does NOT switch branches.

What it produces

  • REVIEW.md in the task directory resolved per _shared/task-dir.md (default $PHP_SRC_DIR/.claude/php-core-dev/review-<short-base>/REVIEW.md) — severity-graded findings.
  • If REVIEW.md exists from a prior run at the same path, it's backed up to REVIEW.md.bak before being overwritten.
  • Slug: review-<short-sha> where <short-sha> is git rev-parse --short <base>. If the base is a branch (e.g. PHP-8.3 — any maintained branch from _shared/branch-detection.md), use review-<branch-slug> instead. Slug is written to .current.

Workflow

1. Pre-checks

test -n "$PHP_SRC_DIR" && test -d "$PHP_SRC_DIR/Zend" || { echo "Run /install"; exit 1; }
cd "$PHP_SRC_DIR"
git status --porcelain          # warn (don't block) if dirty

If the working tree is dirty, note it in REVIEW.md's Scope section — uncommitted changes are part of the diff to review.

2. Determine base ref

BASE=$(git merge-base HEAD origin/master 2>/dev/null || git merge-base HEAD master)

If the user passed an explicit base (PHP-8.3, a SHA, etc.), use that.

If no base can be determined (no master, no origin), stop with:

Cannot determine review base. Pass one explicitly: /review-local <base-ref>

3. Pull the diff

git -C "$PHP_SRC_DIR" diff "$BASE"...HEAD --stat
git -C "$PHP_SRC_DIR" diff "$BASE"...HEAD

Capture:

  • Files changed (count, paths)
  • Lines added / removed (from --stat)
  • The full unified diff (for analysis)

If the diff is empty, stop with No changes between $BASE and HEAD — nothing to review.

4. Backup existing REVIEW.md

Read the full file on GitHub · 139 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 · 139 lines · 102 tokens per session scan A 14ed341d2d2b

Subscribe to this mod's changes

review-local is a skill published in the GitHub repository pronskiy/php-src-developer (8 stars, last pushed 4mo ago), licensed MIT. It adds 102 tokens to every session and 1,722 once invoked, about $0.0004 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-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