A workflow for applying requested changes from a GitHub pull request, which is a proposed code change awaiting review.

Use it with a pull request URL or number, or let it find the pull request connected to the current Git branch and address its review comments.

It turns review feedback into implemented code instead of leaving the developer to find and fix every comment manually.

pr-review — Skill for Claude Code by jellydn

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 jellydn/my-ai-tools --skill pr-review

Clone the repo

git clone --depth 1 https://github.com/jellydn/my-ai-tools

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/jellydn/my-ai-tools/pr-review/github.svg)](https://agentmods.dev/skills/jellydn/my-ai-tools/pr-review)

Your own site

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

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

When invoked 874 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.00011	$0.00874
Opus 5	$0.00005	$0.00437
Sonnet 5	$0.00002	$0.00175
Haiku 4.5	$0.00001	$0.00087

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

Security

Grade A, and why

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 11d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/extract-pr-comments.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

configs/amp/plugins/my-ai-tools-skills/skills/pr-review/SKILL.md · 124 lines

How it starts

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

Fix PR Review Comments

Fix PR review comments by implementing the requested changes.

Usage

/pr-review <PR_URL>      # Review PR by URL (expects full GitHub URL)
/pr-review <PR_NUMBER>   # Review PR by number (expects number, e.g., 123)
/pr-review               # Auto-detect PR from current branch

📋 Argument Handling

The command accepts the PR identifier from $ARGUMENTS:

PR URL: Full GitHub PR URL (e.g., https://github.com/owner/repo/pull/123)
PR Number: Just the PR number (e.g., 123)
No Arguments: Auto-detect the PR associated with the current Git branch

If $ARGUMENTS is provided, use it as the PR identifier. Otherwise, auto-detect the current branch's PR using:

gh pr view --json number,url -q '.number'

This extracts the PR number from the current branch's open PR for use in subsequent commands.

If no open PR is found for the current branch, show this error:

Error: No open pull request found for the current branch.

To review a specific PR:
  /pr-review <PR_URL>
  /pr-review <PR_NUMBER>

Or create a PR first:
  gh pr create

Process

Parse $ARGUMENTS to determine PR identifier (URL, number, or auto-detect)
Fetch PR details and review comments using gh CLI
Parse review comments to understand what needs to be changed
For each comment, implement the fix
Run tests to ensure nothing breaks
Commit the changes

Available Scripts

Extract PR Comments

The extract-pr-comments.js script processes GitHub PR review comments and issue comments to create actionable TODO lists.

# Usage
node $SKILL_PATH/scripts/extract-pr-comments.js <review-comments-file> <issue-comments-file> [output-file]

# Example
node $SKILL_PATH/scripts/extract-pr-comments.js \
  pr-4972-review-comments-raw.json \
  pr-4972-issue-comments-raw.json \
  pr-4972-comments.ndjson

What it does:

Filters out comments with replies (likely resolved)
Classifies comments by severity (critical, high, medium, low)
Categorizes comments (security, performance, maintainability, etc.)
Creates 3 output files:
- .ndjson - Structured comment data
- -todo.md - Prioritized TODO list
- -summary.md - Analysis summary with emojis

Read the full file on GitHub · 124 lines

Files

What ships with it

1 file 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.

scripts/extract-pr-comments.js 9.8 KB runs code

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.

11d ago First seen · 124 lines · 11 tokens per session scan A 21ddbe81fdfa

Subscribe to this mod's changes

pr-review is a skill published in the GitHub repository jellydn/my-ai-tools (120 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 874 once invoked, about $0.0001 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.

Claude Code Code review amp codex open-code skills

go-code-review

Use when reviewing Go code for performance, concurrency safety, security vulnerabilities, or readability issues.

unix2dos/skills · 21 tokens

code-simplifier

Use when code has excessive complexity, deep nesting, unused abstractions, or violates YAGNI/KISS/DRY principles and needs simplification or cleanup.

unix2dos/skills · 36 tokens

agent-watchdog

Use when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log, or pasted run summary. Monitor until the other agent is done or blocked, reconstruct what the user asked, independently investigate the same…

BuilderIO/skills · 115 tokens

comet-verify

Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.

rpamis/comet · 32 tokens

agent-design-best-practices

Best practices for designing Claude Code agent files (.claude/agents/.md). This skill should be used when writing or reviewing agent markdown files to ensure proper design with focused domains, correct tool access, reusable definitions, and separation of capabilities from lifecycle. Combines Anthropic's official…

majiayu000/claude-skill-registry · 73 tokens

graphify-dotnet

Use graphify-dotnet to generate codebase knowledge graphs, architecture snapshots, and exportable repository maps from .NET or polyglot source trees, with optional AI-enriched semantic relationships. USE FOR: graphify commands; graph JSON, HTML, SVG, Cypher, Markdown, and Obsidian exports; repository map and…

managedcode/dotnet-skills · 125 tokens