What is gh-pr-review?

A process for reviewing GitHub pull requests, which are proposed code changes submitted for discussion and merging.

Use it to review a pull request with the GitHub CLI and produce structured feedback about strengths, risks, and test coverage.

It gathers the pull request details and complete diff, then checks the changes for correctness, security, performance, style, architecture, and tests.

gh-pr-review — Skill for Claude Code and Codex by tao12345666333

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 tao12345666333/ankaloop --skill gh-pr-review

Clone the repo

git clone --depth 1 https://github.com/tao12345666333/ankaloop

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tao12345666333/ankaloop/gh-pr-review/github.svg)](https://agentmods.dev/skills/tao12345666333/ankaloop/gh-pr-review)

Your own site

<a href="https://agentmods.dev/skills/tao12345666333/ankaloop/gh-pr-review"><img src="https://agentmods.dev/badge/skills/tao12345666333/ankaloop/gh-pr-review/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/tao12345666333/ankaloop/gh-pr-review"><img src="https://agentmods.dev/badge/skills/tao12345666333/ankaloop/gh-pr-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 657 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 pass 7 Sept 2026

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.00062	$0.00657
Opus 5	$0.00031	$0.00329
Sonnet 5	$0.00012	$0.00131
Haiku 4.5	$0.00006	$0.00066

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

Security

Grade A, and why

gh-pr-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 12d 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.

.amcp/skills/gh-pr-review/SKILL.md · 85 lines

How it starts

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

GitHub PR Review Skill

Review Pull Requests by fetching the diff, analyzing changes, and posting structured review comments.

Prerequisites

gh CLI authenticated (gh auth status)
Repository must be a git clone with a GitHub remote

Review Workflow

Fetch PR metadata: Run gh pr view <number> --json title,body,files,additions,deletions,author,baseRefName,headRefName
Fetch the diff: Run gh pr diff <number> to get the full diff
Analyze the changes by category:
- Architecture: New files/modules, structural decisions
- Correctness: Logic bugs, edge cases, error handling
- Security: Input validation, secrets, auth
- Performance: Unnecessary allocations, N+1 queries, blocking I/O
- Style: Naming, consistency with codebase conventions
- Tests: Coverage, edge cases, test quality
Produce a structured review (see format below)

Review Output Format

## PR Review: <title>

**PR**: #<number> | **Author**: <author> | **Branch**: <head> → <base>
**Files changed**: <count> | **+<additions>** / **-<deletions>**

### Summary
<1-2 sentence overview of what this PR does>

### 👍 Strengths
- <what's done well>

### 🔍 Issues Found

#### Critical
- [ ] <file>:<line> — <description>

#### Suggestions
- [ ] <file>:<line> — <description>

#### Nits
- <minor style/naming suggestions>

### 📋 Checklist
- [ ] Tests added/updated
- [ ] No secrets or credentials
- [ ] Error handling adequate
- [ ] Documentation updated if needed

### Verdict
<APPROVE | REQUEST_CHANGES | COMMENT> — <reasoning>

Posting the Review

After generating the review, offer to post it as a PR comment:

gh pr review <number> --comment --body "<review content>"

Or for approve/request-changes:

gh pr review <number> --approve --body "<review content>"
gh pr review <number> --request-changes --body "<review content>"

Tips

For large PRs (>500 lines), focus on architectural decisions and critical issues first
Check for consistency with the existing codebase patterns
Look at test coverage relative to the complexity of changes
Use gh pr checks <number> to see CI status
When reviewing Python, pay attention to type hints, docstrings, and error handling

Read the full file on GitHub · 85 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

12d ago First seen · 85 lines · 62 tokens per session scan A 913f63cf33ff

Subscribe to this mod's changes

gh-pr-review is a skill published in the GitHub repository tao12345666333/ankaloop (48 stars, last pushed 13d ago), licensed Apache-2.0. It adds 62 tokens to every session and 657 once invoked, about $0.0003 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-30.

Autonomous Agents Code review Git and workflow agent-client-protocol ai-agent ai-coding-assistant cli coding-agent

gh-find-prs

Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.

Hmbown/CodeWhale · 27 tokens

triage

Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.

QwenLM/qwen-code · 50 tokens

vhs-e2e-gif

Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…

dimetron/pi-go · 106 tokens

gh-pr-review