validate-pr

validate-pr is a skill for Claude Code, Codex from arraydude/agent-skills. It costs 128 tokens per session (1,051 once invoked), scanned A, original, MIT.

A process for checking whether AI-generated pull-request review comments are supported by the actual code changes. A pull request is a proposed set of repository changes submitted for review before merging.

In plain words
What is it for?
Use it to validate review comments, identify hallucinated findings, rank issues by priority, and create an action list before merging a pull request.
Why use it?
It helps distinguish real problems from irrelevant comments or claims that the reviewer invented. Each comment is compared with the pull request’s actual diff, which is the line-by-line change list.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

Good fit Use it to validate review comments, identify hallucinated findings, rank issues by priority, and create an action list before merging a pull request.

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

Made for: Claude Code, Codex.

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 validate-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/arraydude/agent-skills/validate-pr/github.svg)](https://agentmods.dev/skills/arraydude/agent-skills/validate-pr)
Your own site
<a href="https://agentmods.dev/skills/arraydude/agent-skills/validate-pr"><img src="https://agentmods.dev/badge/skills/arraydude/agent-skills/validate-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 validate-pr

Your own site · 80×15
<a href="https://agentmods.dev/skills/arraydude/agent-skills/validate-pr"><img src="https://agentmods.dev/badge/skills/arraydude/agent-skills/validate-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 128 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,051 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.00128 $0.01051
Opus 5.5 $0.00051 $0.00420
Sonnet 5.5 $0.00026 $0.00210
Haiku 4.5 $0.00013 $0.00105

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

Security

Grade A, and why

validate-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.

skills/validate-pr/SKILL.md · 102 lines

How it starts

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

Validate PR Comments

Validate AI-generated PR review comments on a pull request — determine which are accurate, which are low-priority noise, and which are hallucinations — by cross-referencing every comment against the actual diff.

When to Apply

Reference these guidelines when:

  • The user wants AI/bot review comments on a PR checked for accuracy
  • Triaging which review feedback is worth addressing before merge
  • Separating genuine findings from hallucinations or misread intent
  • Producing a prioritized action list from a noisy automated review

Prerequisite: the gh CLI must be installed and authenticated.

Rule Categories by Priority

Priority Category Impact Prefix
1 Setup & Input CRITICAL setup-
2 Data Gathering CRITICAL fetch-
3 Validation CRITICAL validate-
4 Output HIGH output-

Quick Reference

1. Setup & Input (CRITICAL)

  • setup-gh-cli - Verify the gh CLI is installed and authenticated before anything else
  • setup-resolve-pr - Resolve the PR from the user's message (number/URL) or fall back to the current branch

2. Data Gathering (CRITICAL)

  • fetch-pr-data - Fetch comments, reviews, body, title, and files in one gh pr view --json call
  • fetch-complete-coverage - Also pull inline review-thread comments; review ALL of them, never a sample

3. Validation (CRITICAL)

  • validate-against-diff - Cross-reference each comment against the real diff and referenced files
  • validate-hallucination - Classify each comment: Valid / Low Priority / Hallucination / Addressed
  • validate-worth-addressing - Judge whether a technically-true comment is actually worth the change

4. Output (HIGH)

  • output-summary-table - Present a priority-sorted table with fixed assessment labels
  • output-followup-details - Expand a single item (comment ID, assessment, verdict) on request

Core Workflow

  1. Setup — Confirm gh is available and authenticated; resolve which PR to validate.
  2. Fetch — Pull all PR data plus inline review comments; count them so nothing is dropped.
  3. Validate — For each comment, cross-reference the diff, decide hallucination vs. valid, and weigh whether it is worth addressing.
  4. Report — Emit the priority-sorted summary table, then expand any item the user asks about.

Read the full file on GitHub · 102 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 · 102 lines · 128 tokens per session scan A 2666169729b9

Subscribe to this mod's changes

validate-pr is a skill published in the GitHub repository arraydude/agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 128 tokens to every session and 1,051 once invoked, about $0.0005 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