Agent skill

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

View SKILL.md on GitHub Repository
Stars 589
Forks 54

Install this agent skill to your Project

npx add-skill https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/github-dev/skills/review-pr

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 and high signal.

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

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

fcakyon/claude-codex-settings

hetzner-deploy

This skill should be used when user asks to "deploy to Hetzner", "create Hetzner server", "manage Hetzner Cloud", "hcloud CLI", or works with Hetzner Cloud infrastructure including servers, networks, firewalls, load balancers, DNS zones, and volumes.

589 54
Explore
fcakyon/claude-codex-settings

pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

589 54
Explore
fcakyon/claude-codex-settings

docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

589 54
Explore
fcakyon/claude-codex-settings

xlsx

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

589 54
Explore
fcakyon/claude-codex-settings

pptx

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

589 54
Explore
fcakyon/claude-codex-settings

dokploy-deploy

This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".

589 54
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results