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 antiwork in antiwork/gumroad

Review GitHub pull requests for the Gumroad codebase against project guidelines, code quality, and correctness.

MITAuto-check passedDevelopment

Install Review PR

skills CLI
$ npx skills add antiwork/gumroad --skill review-pr -a claude-code

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

GitHub CLI
$ gh skill install antiwork/gumroad 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/antiwork/gumroad.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
9.8k
Token cost
~1.2k tokens
SKILL.md length
516 words
Files
2 (incl. references)
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Review GitHub pull requests for the Gumroad codebase against project guidelines, code quality, and correctness.

  • Works in 6 steps: Fetch PR Context → Understand the Change → Review → …
  • The user wants to review a PR
  • SKILL.md covers Workflow and Important
  • Calls gh

What it does

Review PR is an agent skill from antiwork/gumroad. Review GitHub pull requests for the Gumroad codebase against project guidelines, code quality, and correctness. Use when the user wants to review a PR, check new comments on a PR, provide feedback on code changes, or asks about PR quality. Triggers on: "review PR", "review this PR", "check PR NNN", any GitHub PR URL (e.g. https://github.com/antiwork/gumroad/pull/NNNN), "what's new on the PR", "check comments", "review the diff", "give feedback on this PR", or requests to evaluate code changes in a pull request.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/review-guidance.md`).

It sits in Development, covering Pull requests. It works with GitHub. The licence is MIT.

When your agent uses it

  • The user wants to review a PR
  • Check new comments on a PR
  • Provide feedback on code changes
  • Asks about PR quality

Example prompts

  • “review PR”
  • “review this PR”
  • “check PR NNN”
  • “/review-pr”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Fetch PR Context
  2. Understand the Change
  3. Review
  4. Score and Filter
  5. Report
  6. Iterate

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use gh, 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 1.2k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 132 tokens; SKILL.md has 516 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~132
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.7k

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 passed

The automated check found no risky patterns in SKILL.md.

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 antiwork/gumroad at commit fe890ec, republished under its MIT licence (© antiwork). 516 words, ~1,240 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
Review GitHub pull requests for the Gumroad codebase against project guidelines, code quality, and correctness. Use when the user wants to review a PR, check new comments on a PR, provide feedback on code changes, or asks about PR quality. Triggers on: "review PR", "review this PR", "check PR #NNN", any GitHub PR URL (e.g. https://github.com/antiwork/gumroad/pull/NNNN), "what's new on the PR", "check comments", "review the diff", "give feedback on this PR", or requests to evaluate code changes in a pull request.

PR Review

Review pull requests for code quality, correctness, and CONTRIBUTING.md compliance.

Scope boundary: This skill evaluates how the code is written. For evaluating whether the PR solves the right problem, use the issue-detective skill instead.

Workflow

1. Fetch PR Context
bash
gh pr view <number> --repo antiwork/gumroad
gh pr diff <number> --repo antiwork/gumroad
gh pr view <number> --repo antiwork/gumroad --comments
gh api repos/antiwork/gumroad/pulls/<number>/comments

Also read CONTRIBUTING.md from the repo root — it's the source of truth for all guideline checks.

Note PR status (draft, closed, merged). Skip review if merged or closed unless user insists.

2. Understand the Change

From the diff and description, determine:

  • What changed and why (read the linked issue if referenced)
  • Bug fix, feature, refactor, or chore
  • Which layers are affected (frontend, backend, both, tests only)
  • Size and complexity

Read key modified files in full when the diff alone is insufficient to understand context.

3. Review

Run these review passes on the diff:

Pass 1 — Bugs and Logic Errors Wrong conditionals, missing edge cases, race conditions, nil/null handling, off-by-one errors, security vulnerabilities (injection, XSS, CSRF). Focus on code paths introduced or modified by the PR.

Pass 2 — CONTRIBUTING.md Compliance Check the diff against every applicable rule in CONTRIBUTING.md (code standards, naming conventions, testing standards, Sidekiq patterns, PR structure, etc.). The file is the single source of truth — do not maintain a separate checklist.

Pass 3 — Code Clarity Evaluate readability and maintainability of new/modified code. See references/review-guidance.md for what to flag vs what to leave alone. The goal is clear, explicit code — not clever or compact code.

Pass 4 — PR Structure AI disclosure, description quality (explains why), before/after media, test results, appropriate size — all per CONTRIBUTING.md.

⛔ Media evidence is a BLOCKING check (CONTRIBUTING.md line 17 — a hard Must). If the PR touches product/UI (any view, component, CSS, layout, mobile behavior, user-visible copy) and has no before/after video or screenshots, raise it as a critical finding at confidence 95+ and set the Verdict to request-changes. Do NOT wave through a mobile/CSS/layout PR just because the prose description is clear — "the code looks right" is not a substitute for visual proof. A missing video on a non-visual change (no walkthrough) is at least an important finding. This does not apply to PRs that only touch documentation or agent skill files — the diff itself is the reviewable artifact, so do not raise a missing-media finding for docs- or skill-only PRs.

Show full SKILL.md (139 more words)Show less
4. Score and Filter

Assign each finding a confidence score (0–100): how likely is this a genuine problem?

Keep findings >= 80. Drop findings below 80.

See references/review-guidance.md for noise filtering rules and severity levels.

5. Report
## Summary

[1-2 sentences: what the PR does and overall assessment]

## Issues

### [critical|important|suggestion] Title
**File:** `path/to/file.rb:NN`
**Confidence:** NN/100

[Concise explanation and fix suggestion if straightforward.]

...

## Checklist

[CONTRIBUTING.md items that are missing — e.g., no AI disclosure, no before/after, missing tests]

## Verdict

[approve / request-changes / comment-only — with brief justification]

Write the review to gh-pr-review.md in the repo root. Do NOT stage or commit. Do NOT post to GitHub.

6. Iterate

When the user asks to re-check a PR (new comments, updated diff):

bash
gh pr view <number> --repo antiwork/gumroad --comments
gh api repos/antiwork/gumroad/pulls/<number>/comments
gh pr diff <number> --repo antiwork/gumroad

Focus on what changed since the last review. Don't repeat prior findings unless still unaddressed.

Important

  • Use gh read-only only. Never approve, comment on, or request changes via CLI.
  • Review what the PR introduces — not pre-existing code.
  • Be direct and concise. No filler praise.
  • Prioritize substantive issues over cosmetic ones.
  • When unsure, state uncertainty rather than false confidence.
  • For large PRs (1k+ lines), note the PR should be broken up.

© antiwork, MIT. 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 (references) in .agents/skills/review-pr of antiwork/gumroad.

  • SKILL.md
  • references/review-guidance.md

Open the folder on GitHubat commit fe890ec

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 skillantiwork/gumroad9.8k—~1.2kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
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

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k 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

  • 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

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

More from antiwork/gumroad

  • Gumroad Prod Console

    antiwork/gumroad

    Execute read-only Ruby/Rails commands against Gumroad's production database for debugging and investigation.

    9.8k GitHub stars~2.9k tokensUpdated today
    Auto-check: notes

  • Email Blast

    antiwork/gumroad

    Send one-off email blasts to Gumroad creators directly via production console, no PR or deploy needed.

    9.8k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Commit

    antiwork/gumroad

    Stage and commit changes with a clear, concise commit message.

    9.8k GitHub stars~503 tokensUpdated today
    Auto-check passed

  • Create Issue

    antiwork/gumroad

    Draft GitHub issues for the Gumroad codebase. An agent skill from antiwork/gumroad.

    9.8k GitHub stars~747 tokensUpdated today
    Auto-check passed

  • Test Confidence

    antiwork/gumroad

    AI-driven test execution. An agent skill from antiwork/gumroad.

    9.8k GitHub stars~738 tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Review PR

What does Review PR do?

Review GitHub pull requests for the Gumroad codebase against project guidelines, code quality, and correctness. Review PR is an agent skill from antiwork/gumroad. Review GitHub pull requests for the Gumroad codebase against project guidelines, code quality, and correctness.

When should I use Review PR?

Review PR fits situations like: the user wants to review a PR; check new comments on a PR; provide feedback on code changes; asks about PR quality.

How do I install Review PR in Claude Code?

Run `npx skills add antiwork/gumroad --skill review-pr -a claude-code`. Or copy the skill folder (.agents/skills/review-pr in antiwork/gumroad) 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 antiwork/gumroad --skill review-pr -a codex`. Or copy the skill folder (.agents/skills/review-pr in antiwork/gumroad) 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 antiwork/gumroad --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).

Does Review PR access the network?

SKILL.md contains no URLs. Its commands use gh, 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 no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Review PR use?

Review PR is published under the MIT 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 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 457 tokens, read only when the agent opens those files.

What are the alternatives to Review PR?

Skills that share tags, products or a category with Review PR: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k 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?

antiwork (a GitHub organization) maintains it in antiwork/gumroad, which has 9,835 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 10, 2026.

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