Review PR Codex
Review a requested pull request or branch diff read-only in this Codex session. Use when the user asks for review-pr-codex or a Codex PR review.
Install
npx skills add Magnus-Gille/claude-skills --skill review-pr-codexgit clone --depth 1 https://github.com/Magnus-Gille/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/codex/review-pr-codex ~/.claude/skills/review-pr-codexPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Review PR With Codex Perform this review directly in the current Codex session. Do not shell out recursively to `codex exec` unless the user explicitly requests a separate child Codex run. ## Workflow 1. Determine the scope. - For a PR number, run `gh pr view <number> --json baseRefName,headRefName,title,url`. - For a branch, resolve its intended base from the PR or remote metadata. - Without an argument, use the current branch's open PR when available; otherwise discover the remote default branch instead of assuming `main`. Stop clearly if no reliable base exists. 2. Read the selected diff and nearby code in proportion to its size. Start with changed files, direct callers, and tests. Keep the review read-only. 3. Review for bugs/regressions, security, API/doc/config drift, error paths, tests, and deployment or portal contracts when they are in scope. 4. Present grounded findings first, ordered by severity, with file/line, evidence, impact, and a concrete fix. Say clearly when no findings are supported and include residual test gaps. 5. If the user explicitly asks to fix findings, or the already-authorized task includes fixing them, implement them and run focused tests; otherwise do not modify, commit, merge, push, or post comments. The review process itself remains read-only. Do not invent findings from names or conventions alone. Confirm the path is reachable and the claimed behavior is affected by the reviewed change.
Details
- Skill name
review-pr-codex- Repository
- Magnus-Gille/claude-skills
- Path
codex/review-pr-codex/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Review PR Codex skill do?
Review a requested pull request or branch diff read-only in this Codex session. Use when the user asks for review-pr-codex or a Codex PR review.
How do I install the Review PR Codex skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Magnus-Gille/claude-skills --skill review-pr-codex. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Review PR Codex popular?
It lives in Magnus-Gille/claude-skills, which has 5 GitHub stars and 0 forks.
Related skills
Close
5Magnus-Gille/claude-skills
Close a coding-agent session or produce its final handoff only when the user explicitly asks to close, wrap up, or produce an end-of-session handoff.
Cloudflare Private Static Site
5Magnus-Gille/claude-skills
Create, preview, test, release, verify, or roll back a small static Cloudflare site protected by per-person HTTP Basic Auth. Use for private briefings, reports, one-pagers, document portals, or similar sites that should go from finished content to a custom domain in about ten minutes. Do not use for full applications or when the user requires SSO, identity lifecycle, or Cloudflare Access policy management.
Code Friction
5Magnus-Gille/claude-skills
Capture a small, opt-in set of concrete code-changeability observations during a coding task and hand them to Close without affecting readiness.
Architecture Diagram
9Lord1Egypt/RA-Skills
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
Project Validator
5tomada1114/tomada-claude-plugins
Check a Node project for the setup failures that surface later as confusing runtime errors — malformed package.json, uninstalled node_modules, missing .env, uninitialized git — and scaffold the missing pieces. Use when onboarding to an unfamiliar repo, bootstrapping a new project, or diagnosing "it works on my machine".
Browserbase CLI
9Lord1Egypt/RA-Skills
Use the Browserbase CLI (`browse`) for Browserbase Functions and platform API workflows. Use when the user asks to run `browse`, deploy or invoke functions, manage sessions, projects, contexts, or extensions, fetch a page through the Browserbase Fetch API, search the web through the Browserbase Search API, or scaffold starter templates. Prefer the Browser skill for interactive browsing; use the top-level `browse` driver commands (`browse open`, `browse get`, etc.) only when the user explicitly wants the CLI path.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.