review-pr

review-pr is a skill for Claude Code from miltonian/cartographer. It costs 49 tokens per session (942 once invoked), scanned A, original, MIT.

A pull-request review workflow that places changed code on a map of the project’s entities and relationships.

In plain words
What is it for?
Use it to inspect a pull request’s changed files, understand what they do, and compare them with an existing project map.
Why use it?
It helps reviewers see which parts of a codebase a proposed change may affect and follow the review path.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: model in frontmatter.

Part of the cartographer plugin — 5 skills, 1 command, 1 agent, 1 hook, 1 MCP server shipped together

Good fit Use it to inspect a pull request’s changed files, understand what they do, and compare them with an existing project map.

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

Made for: Claude Code.

Or install cartographer, the plugin that ships this one along with the rest of its 5 skills, 1 command, 1 agent, 1 hook, 1 MCP server.

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/miltonian/cartographer/review-pr/github.svg)](https://agentmods.dev/skills/miltonian/cartographer/review-pr)
Your own site
<a href="https://agentmods.dev/skills/miltonian/cartographer/review-pr"><img src="https://agentmods.dev/badge/skills/miltonian/cartographer/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/miltonian/cartographer/review-pr"><img src="https://agentmods.dev/badge/skills/miltonian/cartographer/review-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 942 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.00049 $0.00942
Opus 5.5 $0.00020 $0.00377
Sonnet 5.5 $0.00010 $0.00188
Haiku 4.5 $0.00005 $0.00094

Measured 1mo ago against content hash 234d6632ca40, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

plugin/skills/review-pr/SKILL.md · 114 lines

How it starts

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

PR Review on Cartographer Map

Overlay a pull request onto the existing world-model so the user can spatially understand what the PR changes and what it affects.

Prerequisite: The codebase must already have a world-model. If cartographer_get_summary returns 0 entities, tell the user to run /cartographer analyze first.

Steps

1. Set project

Call cartographer_set_project with the project root path.

2. Get the PR diff

Use $ARGUMENTS as the PR identifier (number, branch name, or URL).

gh pr diff $ARGUMENTS --name-only

This gives you the list of changed files. If the user didn't provide a PR number, check if there's a current branch with an open PR:

gh pr view --json number,title,headRefName

3. Read the diff details

For each changed file (or the most important ones if there are many):

gh pr diff $ARGUMENTS

Understand what actually changed — not just which files, but what the changes DO.

4. Match changes to world-model entities

Call cartographer_query to find entities in the model. Match by:

  • Entity names that correspond to changed functions/components
  • Evidence anchors that reference the changed file paths
  • Relationships involving changed entities

If a changed file doesn't match any entity in the model, note it — the model may need updating.

5. Determine review order

Order the affected entities from primary change to downstream impact:

  1. Core change — the main entity the PR modifies (what the PR is "about")
  2. Supporting changes — entities that changed to support the core
  3. Affected consumers — entities that read/invoke the changed ones (blast radius)

6. Create the PR changeset

Use kind: "changeset" and changeType on each step so the map renders change-type indicators (green=added, amber=modified, red=removed, gray=affected).

cartographer_write_slice(
  name: "PR #123: Add auth middleware",
  description: "Adds authentication checks before write operations",
  kind: "changeset",
  steps: [
    { entityId: "capability:requireAuth", changeType: "added", label: "new auth middleware" },
    { entityId: "capability:registerTools", changeType: "modified", label: "added auth check before handler" },
    { entityId: "entity:WorldModelStore", changeType: "affected", label: "writes now require auth" },
    { entityId: "capability:broadcast", changeType: "affected", label: "receives only authed writes" }
  ],
  evidence: {
    anchors: [{ filePath: "...", lineStart: ..., lineEnd: ..., snippet: "..." }],
    confidence: "proven",
    provenance: "deterministic",
    reasoning: "Matched from git diff"
  }
)

Read the full file on GitHub · 114 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 · 114 lines · 49 tokens per session scan A 234d6632ca40

Subscribe to this mod's changes

review-pr is a skill published in the GitHub repository miltonian/cartographer (3 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 942 once invoked, about $0.0002 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

dekko-verify

Sanity-check a suspiciously low or zero call-graph result from dekko (getcallers, getcallees, findusages, impactedtests, unused) before concluding "no callers" or "dead code," or a heritage/throws-provenance result (query supertypes, query subtypes, query throws) that labels something (external) when you expect it to…

aahlijia/dekko · 151 tokens

ch015-verifier

Run CH015 adversarial verification workflows to independently validate security reports, recheck file-line evidence, find false positives, severity errors, missed findings, and dependencies.

ch015/code-pentester · 37 tokens

ch015-pentest

Run CH015 penetration testing workflows for attacker-minded source-code review, exploit scenarios, POC generation, dry-run or live verification, and security findings.

ch015/code-pentester · 35 tokens

dekko-review-context

Give a code-review or PR-description flow a structural head start before reading a diff line by line. Trigger when the user asks for a PR description, a pre-merge summary, or invokes a code-review flow (/code-review, /review, or an equivalent) against a diff in a repo with a .dekko/ directory.

aahlijia/dekko · 74 tokens

codeweb

Inspect mapped callers and impact before changing code, find existing implementations before adding one, and review structural changes after an edit. Use during coding tasks; Codeweb product planning uses a separate workflow.

GhostlyGawd/codeweb · 41 tokens

analyze

A codebase analysis workflow for existing projects. It explores the code, adds outside research, and produces a Markdown report about architecture, technical debt, security, performance, and possible improvements.

cubha/claude-workflow-plugins · 119 tokens