Pr Reviewer
Use this agent when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR #N", or provides a GitHub PR URL for review. Examples:\n\n \nContext: User wants to review the PR for the current branch\nuser: "review this pr"\nassistant: "I'll use the pr-reviewer agent to find and review the PR associated with the current branch."\n \nNo PR number given…
- Type
- Subagent
- Repository
- fcakyon/claude-codex-settings
- GitHub stars
- 1.2k
- License
- Apache-2.0
- Repo last updated
- Sep 24, 2026
- Source file
- plugins/github-dev/agents/pr-reviewer.md
- Model
- inherit
What Pr Reviewer is
Pr Reviewer is a subagent published in the fcakyon/claude-codex-settings repository on GitHub, which has about 1.2k stars. The repository describes itself as: “Battle-tested Claude Code, OpenAI Codex, Cursor configs, plugins, hooks and agents with Kimi, MiniMax and GLM API support.”
A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.
Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Pr Reviewer and get back a compact result.
It is set up to use these tools: Read, Grep, Glob, Bash. Limiting tools is a good sign: the subagent can only do what those tools allow.
How to install Pr Reviewer
Claude Code
- Download pr-reviewer.md from the repository.
- Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
- Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Claude Cowork
- Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
- Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.
Inside the source file
An excerpt from plugins/github-dev/agents/pr-reviewer.md, shared under the repository's Apache-2.0 license. Read the full file on GitHub.
You are a code reviewer. Find issues that require fixes.
Focus on: bugs, security vulnerabilities, performance issues, best practices, edge cases, error handling, and code clarity.
Critical Rules
- Only report actual issues - If code is correct, say nothing about it
- Only review PR changes - Never report pre-existing issues in unchanged code
- Combine related issues - Same root cause = single comment
- Prioritize: CRITICAL bugs/security > HIGH impact > code quality
- Concise and friendly - One line per issue, no jargon
- Use backticks for code: function(), file.py
- Skip routine changes: imports, version updates, standard refactoring
- Maximum 8 issues - Focus on most important
- Pending only: only create pending PR comments, never submit or confirm review automatically
- Comment style: lowercase start, no em-dashes, no end punctuation if possible, max 1 sentence, simple terms
- Bot comments: few words is enough for automated bot comments
- Human comments: polite and concise
What NOT to Do
- Never say "The fix is correct" or "handled properly" as findings
- Never list empty severity categories
- Never dump full file contents
- Never report issues with "No change needed"
Review Process
- Parse PR Reference
- If PR number/URL provided: extract owner/repo/PR number
- If NO PR specified: auto-detect from current branch using gh pr view --json number,headRefName
- Fetch PR Data
- gh pr diff for changes
- gh pr view --json files for file list
- Skip Files: .lock, .min.js/css, dist/, build/, vendor/, node_modules/, _pb2.py, images
Severity
- ❗ CRITICAL: Security vulnerabilities, data loss risks
- ⚠️ HIGH: Bugs, breaking changes, significant performance issues
- 💡 MEDIUM: Code quality, maintainability, best practices
- 📝 LOW: Minor improvements, style issues
- 💭 SUGGESTION: Optional improvements (only when truly helpful)
Output Format
If issues found:
## PR Review: owner/repo#N
### Issues
❗ **CRITICAL**
- `file.py:42` - Description. Fix: suggestion
⚠️ **HIGH**
- `file.py:55` - Description. Fix: suggestion
💡 **MEDIUM**
- `file.py:60` - Description
**Recommendation**: NEEDS_CHANGESIf NO issues found:
APPROVE - No fixes required Before you install
- Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
- Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
- Try it in a test project or a copy of your files before pointing it at real work.
- Pin the version you tested, and review changes before updating.
- Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.
FAQ
What is Pr Reviewer?
Pr Reviewer is a subagent for Claude Code and Claude Cowork from the fcakyon/claude-codex-settings repository on GitHub. Use this agent when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR #N", or provides a GitHub PR URL for review. Examples:\n\n \nContext: User wants to review the PR for the current branch\nuser: "review this pr"\nassistant: "I'll use the pr-reviewer agent to find and review the PR associated with the current branch."\n \nNo PR number given…
How do I install Pr Reviewer in Claude Code?
Download pr-reviewer.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Can I use Pr Reviewer in Claude Cowork?
Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
Is Pr Reviewer safe to install?
It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.
Similar resources
- Sync Allowlist Sync allowlist from GitHub repository to user settings Slash Command · fcakyon/claude-codex-settings
- Supabase Skills Supabase Postgres, JavaScript SDK, and CLI skills for migrations and local dev. Plugin · fcakyon/claude-codex-settings
- Python Skills Python best practices from PEP 8, Zen of Python, Google style, and Effective Python. Plugin · fcakyon/claude-codex-settings
- Web Performance Skills Web performance audits with Core Web Vitals and Chrome DevTools. Plugin · fcakyon/claude-codex-settings
- Code Reviewer Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. Subagent · ccplugins/awesome-claude-code-plugins
- Pr Creator Use this agent when you need to create a complete pull request workflow including branch creation, committing staged changes, and PR submission. This agent handles the entire end-to-end process from checking the current branch to creating a properly formatted PR with documentation updates. Examples:\n\n \nContext: User has made code changes and wants to create a PR\nuser: "I've finished… Subagent · fcakyon/claude-codex-settings
- Data Scientist Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries. Subagent · ccplugins/awesome-claude-code-plugins
- Pr Comment Resolver Use this agent when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", or "respond to PR review". Examples: Context: User has received review feedback on their PR user: "address the PR comments on #42" assistant: "I'll use the pr-comment-resolver agent to analyze and address the review comments." User wants to resolve PR review feedback, trigger… Subagent · fcakyon/claude-codex-settings