What is review-pr-full?

A workflow for reviewing a GitHub pull request through three stages: checking the product decision, verifying the acceptance criteria, and inspecting the code. A pull request is a proposed code change submitted for review before merging.

Running complete reviews of a pull request and recording which review stages have already covered its current commit.

It brings product fit, requirement compliance, and code quality into one repeatable review process.

review-pr-full — Skill for Claude Code by tomzx

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 tomzx/agents --skill review-pr-full

Clone the repo

git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code.

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/tomzx/agents/review-pr-full/github.svg)](https://agentmods.dev/skills/tomzx/agents/review-pr-full)

Your own site

<a href="https://agentmods.dev/skills/tomzx/agents/review-pr-full"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-pr-full/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/tomzx/agents/review-pr-full"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-pr-full.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 2,357 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. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Excessive Agency · line 230
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.

How audits are shown

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.00049	$0.02357
Opus 5	$0.00024	$0.01179
Sonnet 5	$0.00010	$0.00471
Haiku 4.5	$0.00005	$0.00236

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

Security

Grade A, and why

review-pr-full 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 6d 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.

skills/review-pr-full/SKILL.md · 231 lines

How it starts

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

Review PR Full

Runs the complete three-step review pipeline on a single PR: /validate-pr (are we building the right product?), then /verify-pr (does it conform to the acceptance criteria?), then /review-pr (is the code well-crafted?). Each step posts its own report and marks the commit it reviewed.

Staleness checking is handled by the same deterministic Python script used by review-requested-prs (~/.agents/scripts/review_requested_prs.py). It checks both GitHub PR comments and local report files at ~/.sdlc/<owner>/<repo>/pull-requests/<pr>/ for markers, so it works even when should-post-to-github has disabled posting. Only stale steps are run, so re-running after a partial completion picks up where it left off.

Prerequisites

uv installed (for running the Python script)
gh CLI authenticated (used by the script as a token fallback)
validate-pr, verify-pr, and review-pr skills available

Workflow

Resolve PR argument (URL or number + repo)
                |
                v
Run ~/.agents/scripts/review_requested_prs.py --dispatch
                |
                v
  Parse dispatch commands (stale steps for this PR)
                |
                v
  Any stale steps?
   /          \
  No           Yes
   |             |
   v             v
 Report       Create shared worktree
 "up to          |
 date"           v
            Run stale steps sequentially:
              validate-pr -> verify-pr -> review-pr
            Check for blocking verdict after each step
                |
                v
            Clean up worktree
                |
                v
            Report summary

Steps

1. Resolve the PR argument

Accept one of:

A PR URL: https://github.com/owner/repo/pull/42
A PR number with a repository: 42 owner/repo
A PR number alone: 42 (uses $REPO from the environment)

If a PR URL is given, pass it directly to the script. If a PR number and repo are given, construct the URL:

PR_URL="https://github.com/${REPO}/pull/${PR_NUMBER}"

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

6d ago First seen · 231 lines · 49 tokens per session scan A ee064b862232

Subscribe to this mod's changes

review-pr-full is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 2,357 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-09-03.

Code review Git and workflow

review-implement-phase

Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.

prisma/orm · 38 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

verify-behavior

Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…

nicknisi/dotfiles · 68 tokens

github-contributor

End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…

daymade/claude-code-skills · 133 tokens

revdiff

Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…

umputun/revdiff · 248 tokens

write-pr

Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.

tldraw/tldraw · 53 tokens