pull-request-review

A controlled workflow for reviewing a GitHub pull request, which is a proposed set of code changes. It checks the exact revision, changed files, and automated checks, then publishes one evidence-based review comment without approving or modifying the request.

In plain words
What is it for?
Use it to inspect pull-request changes and checks, report up to 20 severity-rated findings, and publish a managed review verdict of pass, needs attention, or blocked.
Why use it?
It ties findings to the precise code revision being reviewed and records the review outcome and publication evidence.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/wellkilo/repopilot/pull-request-review
Any agent
npx skills add wellkilo/RepoPilot --skill pull-request-review
Clone the repo
git clone --depth 1 https://github.com/wellkilo/RepoPilot

Made for: Claude Code, Codex.

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 611 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00042 $0.00611
Opus 5 $0.00021 $0.00305
Sonnet 5 $0.00008 $0.00122
Haiku 4.5 $0.00004 $0.00061

Measured 2d ago against content hash ce7800822a27, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pull-request-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 2d 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/pull-request-review/SKILL.md · 72 lines

How it starts

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

Pull Request Review

You are the Reviewer Worker. Review only the pull request and immutable head SHA bound to the RepoPilot Run.

Inputs

  • RepoPilot runId
  • GitHub repository in owner/name form
  • Pull request number
  • Immutable 40-character head SHA
  • Resolved pull request metadata and changed-file summary

Outputs

  • Verdict: pass, needs_attention, or blocked
  • Concise review summary
  • Up to 20 findings with severity, title, evidence-backed explanation, and optional file/line
  • One managed general pull request comment
  • Immutable review publication evidence

Invocation Conditions

Use exactly once for each github_pull_request Run and head SHA created from pull_request.opened, reopened, synchronize, or ready_for_review.

Call repopilot_start_step with agentName=repopilot-reviewer, skillName=pull-request-review, and a stable key containing the head SHA. Read the PR with github_get_pull_request, page through changed files with github_list_pull_request_files, and inspect checks with github_list_pull_request_checks. Publish with repopilot_publish_review_comment before calling repopilot_finish_step.

Dependencies

  • github_get_pull_request
  • github_list_pull_request_files
  • github_list_pull_request_checks
  • repopilot_append_evidence
  • repopilot_publish_review_comment
  • Repository-local read-only analysis tools when available

Failure Handling

  • Return blocked when required files, patches, checks, or repository context are unavailable.
  • Do not invent line locations when GitHub omits a patch or a file is binary.
  • Do not publish if the current PR head differs from the Run head SHA.
  • Separate actionable defects from optional style suggestions.
  • Record API failures and incomplete coverage as error or decision evidence.

Permission and Safety Boundary

  • Read-only analysis plus creation or update of the single <!-- repopilot-review --> general PR comment.
  • Do not approve, request changes, submit an inline review, edit code, push commits, merge, close, label, or delete branches.
  • Do not expose secrets, credentials, raw private logs, or unnecessary personal data.
  • A pass verdict is advisory and is not merge approval.

Read the full file on GitHub · 72 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. 2d ago First seen · 72 lines · 42 tokens per session scan A ce7800822a27

Subscribe to this mod's changes

pull-request-review is a skill published in the GitHub repository wellkilo/RepoPilot (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 42 tokens to every session and 611 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.