Agent skill · Code Review & Quality

review-pr

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".

fcakyongithub.com/fcakyonGitHub ↗
claude-codecodexcursorApache-2.0
Install
npx skills add fcakyon/claude-codex-settings --skill review-pr --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 2 KB
Bundled scripts: none
Path: plugins/github-dev/skills/review-pr/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 967
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 1. **Preferred execution** - If subagents are available, use `github-dev:pr-reviewer` and pass the PR reference. - Otherwise follow the manual steps below. 2. **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`. 3. **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. 4. **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

What's inside
Steps it walks through
  1. Process
  2. Output Format
More from claude-codex-settings
All skills →
docUse when the task involves reading, creating, or editing `.docx` documents, especially when…DocumentationslidesCreate and edit presentation slide decks (`.pptx`) with PptxGenJS, bundled layout helpers, and…Content & Marketingcodex-advisorThis skill should be used when the user asks for a "GPT second opinion", wants a "cross-model…Code Review & Qualityfable-advisorThis skill should be used when the user asks for a "Fable second opinion", wants to "check a plan…Business & Financeagent-browserAgent-browser usage guide. Read this before running any agent-browser commands. Covers the…SecurityspreadsheetUse when tasks involve creating, editing, analyzing, or formatting spreadsheets (`.xlsx`, `.csv`…Data & Analytics
About this skill
What does the review-pr skill do?

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".

How do I install it?

Run `npx skills add fcakyon/claude-codex-settings --skill review-pr --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From fcakyon/claude-codex-settings, a repository with 967 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.