mcpbeat Sign in

Review Pr Agent Skill

by fcakyon

This skill should be used when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR #N", provides a GitHub PR URL, or explicitly invokes "review-pr".

504 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
955
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/fcakyon/claude-codex-settings --skill review-pr

The instruction itself

3 sections, as written by the author

Review PR

Review a pull request for bugs, regressions, missing tests, and risky changes.

When explicitly invoked with extra text, treat that text as the PR number or URL. If no PR

reference is provided, infer it from the current branch.

Process

  • Preferred execution
  • If subagents are available, use github-dev:pr-reviewer and pass the PR reference.
  • Otherwise follow the manual steps below.
  • Parse PR reference
  • If a PR number or URL is provided, extract owner, repo, and PR number.
  • If not, auto-detect the PR from the current branch with gh pr view --json number,headRefName.
  • Fetch PR data
  • Use gh pr diff <number> for the full diff.
  • Use gh pr view <number> --json files for the changed file list.
  • Skip generated or vendored files such as .lock, .min.js, .min.css, dist/, build/, vendor/, node_modules/, _pb2.py, and images.
  • Review focus
  • Only report issues that require fixes.
  • Only review PR changes, never pre-existing issues in unchanged code.
  • Prioritize bugs, security issues, breaking changes, performance issues, edge cases, and missing tests.
  • Combine related issues that share the same root cause.
  • Keep the list short and high signal.
  • Review comment rules
  • Only create pending PR comments, never submit or confirm the review automatically.
  • Use gh for GitHub operations.
  • Start comments in lowercase, keep them short, avoid end punctuation when possible.
  • Use simple language for both bot-facing and human-facing comments.

Output Format

If issues are found, report them in descending severity with file references and a final

recommendation of NEEDS_CHANGES.

If no issues are found, return APPROVE - No fixes required.

Other skills for the same job

different authors, same section of the catalogue
Receiving Code Review
by ZhanlinCui
×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens
Requesting Code Review
by ZhanlinCui
×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

2k tokens
Git Commit
by github
vendor ×3

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

799 tokens
Github Code Review
by ComeOnOliver
×3

Comprehensive GitHub code review with AI-powered swarm coordination

13k tokens
Karpathy Guidelines
by hyyhf
×3

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

629 tokens
Code Reviewer
by google-gemini
vendor ×2

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

795 tokens
Agent MD Refactor
by softaworks
×2

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

4k tokens
Commit Work
by softaworks
×2

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take fcakyon/review-pr from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.