New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Review PR

by PX4 in PX4/PX4-Autopilot

Substance-focused review of a PX4 pull request — merit, first-principles correctness, architecture fit.

BSD-3-ClauseAuto-check: notesDevelopment

Install Review PR

skills CLI
$ npx skills add PX4/PX4-Autopilot --skill review-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install PX4/PX4-Autopilot review-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/PX4/PX4-Autopilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/review-pr .claude/skills/review-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
review-pr
GitHub stars
13k
Token cost
~1k tokens
SKILL.md length
575 words
Files
2
Skills in repo
6
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

Substance-focused review of a PX4 pull request — merit, first-principles correctness, architecture fit.

  • Tasks that involve Pull requests
  • SKILL.md covers Gather, History (optional), Review and Deliver
  • Calls gh and git

What it does

Review PR is an agent skill from PX4/PX4-Autopilot. Substance-focused review of a PX4 pull request — merit, first-principles correctness, architecture fit. Produces a debrief for the user and a draft review comment.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `review-criteria.md`).

It sits in Development, covering Pull requests. It works with Git. The repository describes itself as: PX4 Autopilot Software. The licence is BSD-3-Clause.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/review-pr”

Requirements

  • Pre-approved tools (allowed-tools): Bash, Read, Glob, Grep, Agent

What it can do on your machine

Read from SKILL.md and the folder at commit a427a2e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Glob
    • Grep
    • Agent

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Review PR loads about 1k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 575 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Glob, Grep, Agent

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from PX4/PX4-Autopilot at commit a427a2e, republished under its BSD-3-Clause licence (© PX4). 575 words, ~1,020 tokens.

Download SKILL.mdSave it as .claude/skills/review-pr/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
review-pr
description
Substance-focused review of a PX4 pull request — merit, first-principles correctness, architecture fit. Produces a debrief for the user and a draft review comment.
allowed-tools
Bash, Read, Glob, Grep, Agent
argument-hint
<PR number or URL>

PX4 Pull Request Review

Goal: brief the user on a PR before they spend their own time on it, and draft a review comment they can choose to post. The review is by the assistant and is presented as such — write from its own frame of reference, not the user's, unless the user explicitly requests a different voice.

Focus on substance only. Do not review commit messages, do not recommend a merge strategy, do not audit formatting (CI enforces it). Be extremely thorough — the user wants a deep understanding of the problem, not just verdicts — but scale effort with impact: roughly proportional to lines/files changed and how flight-critical the touched code is. For diffs too large to hold at once, fan out subagents per subsystem when the client has them.

Gather

In parallel:

  • gh pr view <PR> --json number,title,body,author,baseRefName,files,reviews
  • gh pr diff <PR> — on HTTP 406 (huge diff) do not retry; use gh api repos/{owner}/{repo}/pulls/<PR>/files --paginate and fetch key patches selectively
  • gh pr checks <PR> (exit code 8 just means checks are pending)
  • existing feedback: gh api repos/{owner}/{repo}/pulls/<PR>/comments --paginate --jq '.[] | {user: .user.login, path, body}' (inline) and gh api repos/{owner}/{repo}/issues/<PR>/comments --paginate --jq '.[] | {user: .user.login, body}' (conversation)

Read any linked issue — the claimed problem is the baseline for judging merit. For full post-change file contents without touching the working tree: git fetch origin pull/<PR>/head, then git show FETCH_HEAD:<path>.

History (optional)

When the PR changes existing behavior rather than adding something new, check whether the author has done their homework on the area:

  • Open issues and PRs touching the same code or symptom: gh issue list --search, gh pr list --search. Is this already being worked on, or duplicated?
  • git log -L / git log --follow -p and git blame on the changed lines, then the PRs and issues those commits reference. Was the current behavior intentional, and was the reasoning sound?
  • Deferred work: TODOs, issue threads, or review comments where the change was considered and deliberately postponed or rejected.

Report only what bears on the PR: a reverted decision the author does not acknowledge, conflicting in-flight work, or an unaddressed reason the code is the way it is.

Show full SKILL.md (220 more words)Show less

Review

Apply the criteria in review-criteria.md. Read it before reviewing.

Deliver

End with two things, then stop — do not post anything.

1. Debrief for the user. Lead with the findings — the user wants actionable information, not a play-by-play of the diff. Give only the framing they need to judge the change: whether the claimed problem is real, scope and risk (subsystems touched, flight-critical or not), and what CI and other reviewers already said. Restate what the change actually does and why only when the PR description is missing, ambiguous, or misleading. Order findings by severity (blocker / concern / nit) with file:line.

2. Draft review comment, shown verbatim in a fenced block. First line: **<assistant> review on behalf of @<login>** (e.g. Claude, Codex) (login via gh api user --jq .login). Then terse, actionable findings only — what is wrong, why it matters, what to do, with file:line references. Frame each as an objective engineering tradeoff, not a moral judgment. Never guess: if you cannot demonstrate a flaw via a concrete code path or a first-principles derivation, stay silent. No praise or "verified OK" notes unless they change what the author should do, no meta sections, no conversational filler, nothing already raised by others.

If the user asks to post it, post the draft verbatim with gh pr comment <PR> --body "$(cat <<'EOF' ... EOF)".

© PX4, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/review-pr of PX4/PX4-Autopilot.

  • SKILL.md
  • review-criteria.md

Open the folder on GitHubat commit a427a2e

Compare with similar skills

Review PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Review PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review PR this skillPX4/PX4-Autopilot13k—~1kAutomated safety check: NotesBSD-3-Clause
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Open Code Review CLIalibaba/open-code-review45k—~3.1kAutomated safety check: PassApache-2.0
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    45k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

More from PX4/PX4-Autopilot

  • Build Px4 macOS

    PX4/PX4-Autopilot

    Build PX4 board firmware on macOS in the px4-dev Docker container, including git worktrees, and stage commit-labeled artifacts without flashing hardware.

    13k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Rebase Onto Main

    PX4/PX4-Autopilot

    Rebase a branch onto main, handling squash-merged parent branches cleanly

    13k GitHub stars~1.1k tokensUpdated today
    Auto-check: notes

  • Build Px4 Linux

    PX4/PX4-Autopilot

    Build PX4 firmware or SITL natively on a Linux host, in the current checkout, without flashing hardware.

    13k GitHub stars~385 tokensUpdated today
    Auto-check passed

  • Commit

    PX4/PX4-Autopilot

    Create a conventional commit for PX4 changes. An agent skill from PX4/PX4-Autopilot.

    13k GitHub stars~527 tokensUpdated today
    Auto-check: notes

  • PR

    PX4/PX4-Autopilot

    Create a pull request with conventional commit title and description

    13k GitHub stars~581 tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Review PR

What does Review PR do?

Substance-focused review of a PX4 pull request — merit, first-principles correctness, architecture fit. Review PR is an agent skill from PX4/PX4-Autopilot. Substance-focused review of a PX4 pull request — merit, first-principles correctness, architecture fit.

When should I use Review PR?

Review PR fits situations like: tasks that involve Pull requests.

How do I install Review PR in Claude Code?

Run `npx skills add PX4/PX4-Autopilot --skill review-pr -a claude-code`. Or copy the skill folder (.agents/skills/review-pr in PX4/PX4-Autopilot) into .claude/skills/review-pr in your project. Claude Code loads it when a task matches its description.

How do I install Review PR in Codex?

Run `npx skills add PX4/PX4-Autopilot --skill review-pr -a codex`. Or copy the skill folder (.agents/skills/review-pr in PX4/PX4-Autopilot) into .agents/skills/review-pr in your project. Codex loads it when a task matches its description.

Can I use Review PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PX4/PX4-Autopilot --skill review-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-pr, .gemini/skills/review-pr, .github/skills/review-pr and .opencode/skills/review-pr in your project.

What does Review PR need to run?

Going by SKILL.md and its folder, Review PR needs the command-line tools its instructions call (gh and git). Its frontmatter pre-approves these tools: Bash, Read, Glob, Grep, Agent.

Does Review PR access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Review PR safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Review PR use?

Review PR is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review PR use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Review PR?

Skills that share tags, products or a category with Review PR: Finishing a Development Branch (obra/superpowers, 297k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Open Code Review CLI (alibaba/open-code-review, 45k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review PR?

PX4 (a GitHub organization) maintains it in PX4/PX4-Autopilot, which has 12,763 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 8, 2026.

Source: PX4/PX4-Autopilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.