Agent skill

PR Review

by jellydn in jellydn/my-ai-tools

Fix PR review comments by implementing requested changes. An agent skill from jellydn/my-ai-tools.

MITAuto-check passedDevelopment

Install PR Review

skills CLI
$ npx skills add jellydn/my-ai-tools --skill pr-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jellydn/my-ai-tools pr-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pr-review .claude/skills/pr-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pr-review
GitHub stars
123
Token cost
~1.1k tokens
SKILL.md length
309 words
Files
2 (incl. scripts)
Skills in repo
33
Repo updated
First seen
Licence
MIT

At a glance

Fix PR review comments by implementing requested changes. An agent skill from jellydn/my-ai-tools.

  • Works in 3 steps: PR URL: Full GitHub PR URL (e.g.,… → PR Number: Just the PR number (e.g., 123) → No Arguments: Auto-detect the PR…
  • Tasks that involve Pull requests
  • SKILL.md covers Usage, Process, Available Scripts and Examples
  • Runs JavaScript scripts from its folder; calls gh and node; reaches github.com

What it does

PR Review is an agent skill from jellydn/my-ai-tools. Fix PR review comments by implementing requested changes

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/extract-pr-comments.js`). Compatibility notes: cline, claude, opencode, amp, codex, gemini, cursor, pi

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: Comprehensive configuration management for AI coding tools - Replicate my complete setup for Claude Code, OpenCode, Amp, Li, Codex and Claude Code Switch with custom… The licence is MIT.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/pr-review”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

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

What it can do on your machine

Read from SKILL.md and the folder at commit 62c9227. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • gh
    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    cline, claude, opencode, amp, codex, gemini, cursor, pi

    From compatibility in the SKILL.md frontmatter.

Context cost

PR Review loads about 1.1k tokens when it runs. Until then it costs about 17 tokens; SKILL.md has 309 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~17
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jellydn/my-ai-tools at commit 62c9227, republished under its MIT licence (© jellydn). 309 words, ~1,063 tokens.

Download SKILL.mdSave it as .claude/skills/pr-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
pr-review
description
Fix PR review comments by implementing requested changes
compatibility
cline, claude, opencode, amp, codex, gemini, cursor, pi
license
MIT
hint
Use when fixing PR review comments or addressing review feedback. Accepts PR URL, PR number, or auto-detects from current branch
user-invocable
true
metadata.audience
all
metadata.workflow
code-quality

Fix PR Review Comments

Fix PR review comments by implementing the requested changes.

Usage

bash
/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:

  1. PR URL: Full GitHub PR URL (e.g., https://github.com/owner/repo/pull/123)
  2. PR Number: Just the PR number (e.g., 123)
  3. 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:

bash
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:

text
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

  1. Parse $ARGUMENTS to determine PR identifier (URL, number, or auto-detect)
  2. Fetch PR details, review threads, issue comments, and authoritative thread-resolution state using gh
  3. Classify each comment as actionable, informational, disputed/ambiguous, or resolved; ask before changing disputed or ambiguous requests
  4. For each actionable comment, record the comment ID, planned change, and verification command
  5. Implement the approved fixes
  6. Run focused tests, then the relevant broader checks
  7. Recheck the comment-to-change list and confirm every actionable thread is resolved or explicitly deferred
  8. 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.

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

# Example
gh api graphql \
  -f owner=OWNER -f name=REPO -F number=4972 \
  -f query='query($owner:String!, $name:String!, $number:Int!) { repository(owner:$owner, name:$name) { pullRequest(number:$number) { reviewThreads(first:100) { nodes { isResolved comments(first:100) { nodes { databaseId } } } } } } }' \
  > pr-4972-threads.json

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

What it does:

  • Requires a threads file of GitHub review threads and skips a review comment only when its thread has isResolved: true
  • Does not treat a reply as resolution; an unanswered thread stays actionable
  • 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

Severity classification:

  • 🔴 Critical: security, vulnerability, exploit
  • 🟠 High: bug, error, breaking, crash, fail
  • 🟡 Medium: performance, improvement, refactor, optimize
  • 🟢 Low: everything else

Categories:

  • 🔒 Security
  • ⚡ Performance
  • 🔧 Maintainability
  • ♿ Accessibility
  • 🧪 Testing
  • 📚 Documentation
  • 🏷️ Typing
  • 🎨 Style
  • ✨ Code Quality

Examples

bash
# Fix review comments for a PR using URL
/pr-review https://github.com/owner/repo/pull/123

# Fix review comments using PR number
/pr-review 123

# Auto-detect PR from current branch
/pr-review

# After extracting comments with the script, work through the TODO list
# The TODO list is ordered by priority: Critical → High → Medium → Low

© jellydn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in skills/pr-review of jellydn/my-ai-tools.

  • SKILL.md
  • scripts/extract-pr-comments.js

Open the folder on GitHubat commit 62c9227

Compare with similar skills

PR Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

PR Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Review this skilljellydn/my-ai-tools123—~1.1kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from jellydn/my-ai-tools

All 33 skills in this repo
  • Babysit PR

    jellydn/my-ai-tools

    A skill your agent uses when monitoring an open GitHub PR for CI failures, review feedback, mergeability, and safe retries or fixes.

    123 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed
  • Visual PR

    jellydn/my-ai-tools

    Posts a concise visual outline as a GitHub pull request comment.

    123 GitHub stars~764 tokensUpdated yesterday
    Auto-check passed
  • Qmd Knowledge

    jellydn/my-ai-tools

    Manage project knowledge with qmd — captures learnings, decisions, and conventions

    123 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Prd

    jellydn/my-ai-tools

    Generate Product Requirements Documents from feature ideas — plans specs and requirements

    123 GitHub starsUsed in 4 repos~1.8k tokens
    Auto-check passed
  • Capability Experiments

    jellydn/my-ai-tools

    Build an interactive report or experiment when the user asks to explore model capabilities.

    123 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Security Audit

    jellydn/my-ai-tools

    A skill your agent uses when reviewing code for security vulnerabilities, hardening an application, or deriving security requirements from OWASP/ASVS guidance.

    123 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check: notes

Works with

Categories

Questions about PR Review

What does PR Review do?

Fix PR review comments by implementing requested changes. An agent skill from jellydn/my-ai-tools. PR Review is an agent skill from jellydn/my-ai-tools.

When should I use PR Review?

PR Review fits situations like: tasks that involve Pull requests.

How do I install PR Review in Claude Code?

Run `npx skills add jellydn/my-ai-tools --skill pr-review -a claude-code`. Or copy the skill folder (skills/pr-review in jellydn/my-ai-tools) into .claude/skills/pr-review in your project. Claude Code loads it when a task matches its description.

How do I install PR Review in Codex?

Run `npx skills add jellydn/my-ai-tools --skill pr-review -a codex`. Or copy the skill folder (skills/pr-review in jellydn/my-ai-tools) into .agents/skills/pr-review in your project. Codex loads it when a task matches its description.

Can I use PR Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jellydn/my-ai-tools --skill pr-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-review, .gemini/skills/pr-review, .github/skills/pr-review and .opencode/skills/pr-review in your project.

What does PR Review need to run?

Going by SKILL.md and its folder, PR Review needs JavaScript for the scripts in its folder and the command-line tools its instructions call (gh and node). Our summary lists: Node.js. Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi.

Does PR Review access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is PR Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does PR Review use?

PR Review is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PR Review use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to PR Review?

Skills that share tags, products or a category with PR Review: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Review?

jellydn (a GitHub user) maintains it in jellydn/my-ai-tools, which has 123 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 10, 2026.

Source: jellydn/my-ai-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.