A review guide for pull requests and code changes in Common Platform repositories, including HMCTS Crime Common Platform projects. It checks changes against the relevant coding and architecture standards.

Use it to review a pull request or local changes in context services, Spring Boot services, Angular applications, Terraform, Helm charts, architecture models, or UI test repositories.

It helps catch repository-specific problems that a general code review might miss.

review-pr — Skill for Claude Code by hmcts

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 hmcts/agentic-plugins-marketplace --skill review-pr

Clone the repo

git clone --depth 1 https://github.com/hmcts/agentic-plugins-marketplace

Made for: Claude Code.

Or install hmcts-sdlc-orchestrator, the plugin that ships this one along with the rest of its 10 skills, 9 agents.

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/hmcts/agentic-plugins-marketplace/review-pr/github.svg)](https://agentmods.dev/skills/hmcts/agentic-plugins-marketplace/review-pr)

Your own site

<a href="https://agentmods.dev/skills/hmcts/agentic-plugins-marketplace/review-pr"><img src="https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hmcts/agentic-plugins-marketplace/review-pr"><img src="https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/review-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,616 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.00042	$0.01616
Opus 5	$0.00021	$0.00808
Sonnet 5	$0.00008	$0.00323
Haiku 4.5	$0.00004	$0.00162

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

Security

Grade A, and why

review-pr 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 9d 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/agents/hmcts-sdlc-orchestrator/skills/review-pr/SKILL.md · 153 lines

How it starts

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

PR Review for Common Platform

Reviews pull requests against CP coding standards, architectural patterns, and platform conventions.

When to Use

User asks to "review this PR", "check this pull request", "review PR #123"
User pastes a PR URL or number
User asks for feedback on changes before creating a PR

Process

Step 1: Gather Changes

If given a PR URL or number:

gh pr view <number> --json title,body,files,additions,deletions,baseRefName,headRefName
gh pr diff <number>

If reviewing local changes:

git diff main...HEAD
git log main..HEAD --oneline

Step 2: Identify Repo Type

Determine the repo type from the directory name and build files:

cpp-context-* with pom.xml → Legacy context service (Maven, CQRS, Java EE)
cpp-mbd-* with build.gradle → Modern by Default service (Gradle, Spring Boot)
cpp-ui-* with package.json → Angular UI application
cpp-terraform-* with *.tf → Terraform module
cpp-helm-chart → Helm chart changes
cp-c4-architecture with .c4 files → Architecture model changes
cpp-ui-e2e-serenity with serenity.properties → UI E2E test repo (Serenity BDD + Cucumber)
cpp-apitests with api-integration-test/ → API integration test repo (JUnit 5 + REST Assured)

Step 3: Apply Repo-Specific Review Criteria

Context Services (Maven/CQRS)

Commands produce domain events (not direct state mutation)
Queries are read-only (no state changes in query handlers)
New viewstore entities have Liquibase migrations with rollback
Event handlers are idempotent
JSON schemas follow naming convention: {context}.{type}.{name}.json
RAML API definitions are updated for new/changed endpoints
At least one integration test per new/changed endpoint (<context>-integration-test/), exercising the real persistence/SQL + event path — not just unit tests that mock the repository
Integration-test suite is green locally (mvn clean && ./runIntegrationTests.sh when present); summary pasted in the PR
No domain logic in controllers or repositories (belongs in aggregates/handlers)
Framework interceptors not bypassed without justification

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

9d ago First seen · 153 lines · 42 tokens per session scan A d62092abea0b

Subscribe to this mod's changes

review-pr is a skill published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 1,616 once invoked, about $0.0002 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-08-31.

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