A review process that compares recent code changes with both the project's coding standards and the original requirements.

Use it to review changes against a branch, commit, tag, or other fixed point, using the related issue or product specification when available.

It can reveal code-quality problems as well as differences between what was built and what was requested.

review — Skill for Claude Code by appleweiping

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 appleweiping/WEIPING_WIKI --skill review

Clone the repo

git clone --depth 1 https://github.com/appleweiping/WEIPING_WIKI

Made for: Claude Code.

Or install mattpocock-skills, the plugin that ships this one along with the rest of its 28 skills.

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/appleweiping/weiping_wiki/review/github.svg)](https://agentmods.dev/skills/appleweiping/weiping_wiki/review)

Your own site

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

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

When invoked 1,052 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 100% copy Near-identical to another mod 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.00095	$0.01052
Opus 5	$0.00048	$0.00526
Sonnet 5	$0.00019	$0.00210
Haiku 4.5	$0.00010	$0.00105

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

Security

Grade A, and why

review 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 10d 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.

Origin

This is a copy

100% identical to review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/mattpocock-skills/skills/in-progress/review/SKILL.md · 79 lines

How it starts

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

Review

Two-axis review of the diff between HEAD and a fixed point the user supplies:

Standards — does the code conform to this repo's documented coding standards?
Spec — does the code faithfully implement the originating issue / PRD / spec?

Both axes run as parallel sub-agents so they don't pollute each other's context, then this skill aggregates their findings.

The issue tracker should have been provided to you — run /setup-matt-pocock-skills if docs/agents/issue-tracker.md is missing.

Process

1. Pin the fixed point

Whatever the user said is the fixed point — a commit SHA, branch name, tag, main, HEAD~5, etc. Don't be opinionated; pass it through. If they didn't specify one, ask: "Review against what — a branch, a commit, or main?" Don't proceed until you have it.

Capture the diff command once: git diff <fixed-point>...HEAD (three-dot, so the comparison is against the merge-base). Also note the list of commits via git log <fixed-point>..HEAD --oneline.

2. Identify the spec source

Look for the originating spec, in this order:

Issue references in the commit messages (#123, Closes #45, GitLab !67, etc.) — fetch via the workflow in docs/agents/issue-tracker.md.
A path the user passed as an argument.
A PRD/spec file under docs/, specs/, or .scratch/ matching the branch name or feature.
If nothing is found, ask the user where the spec is. If they say there isn't one, the Spec sub-agent will skip and report "no spec available".

3. Identify the standards sources

Anything in the repo that documents how code should be written. Common locations:

CLAUDE.md, AGENTS.md
CONTRIBUTING.md
CONTEXT.md, CONTEXT-MAP.md, per-context CONTEXT.md files
docs/adr/ (architectural decisions are standards)
.editorconfig, eslint.config.*, biome.json, prettier.config.*, tsconfig.json (machine-enforced standards — note them but don't re-check what tooling already checks)
Any STYLE.md, STANDARDS.md, STYLEGUIDE.md, or similar at the repo root or under docs/

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

10d ago First seen · 79 lines · 95 tokens per session scan A 5700f30d3f06

Subscribe to this mod's changes

review is a skill published in the GitHub repository appleweiping/WEIPING_WIKI (122 stars, last pushed 14d ago), licensed MIT. It adds 95 tokens to every session and 1,052 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to review, differing in 0 lines, and is treated as a copy.

Code review

autoreview

Pre-commit/ship code review: Codex default; optional Claude or Pi.

openclaw/clawhub · 20 tokens

rework-rate

Measure and interpret PR rework rate — the emerging 5th DORA metric.

bradygaster/squad · 20 tokens

omh-code-review

This is a Hermes-native code-review workflow skill.

rlaope/oh-my-hermes · 46 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

code-reviewer

Code review specialist focused on patterns, bugs, security, and performance.

RightNow-AI/openfang · 17 tokens

agent-teams-simplify-and-harden

Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…

LeoYeAI/openclaw-master-skills · 115 tokens