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

Reviewing PRs

by portabletext in portabletext/editor

Review a PR in this repo against the house conventions before it is marked ready.

MITAuto-check passedDevelopment

Install Reviewing PRs

skills CLI
$ npx skills add portabletext/editor --skill reviewing-prs -a claude-code

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

GitHub CLI
$ gh skill install portabletext/editor reviewing-prs --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/portabletext/editor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/reviewing-prs .claude/skills/reviewing-prs && 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
reviewing-prs
GitHub stars
280
Token cost
~940 tokens
SKILL.md length
490 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Review a PR in this repo against the house conventions before it is marked ready.

  • Asked to review
  • SKILL.md covers Gather, Route each artifact to its skill, Verify claims empirically and Report, plus 1 more section
  • Calls gh and git
  • Check a PR (review this PR

What it does

Reviewing PRs is an agent skill from portabletext/editor. Review a PR in this repo against the house conventions before it is marked ready. Use when asked to review, pre-flight, or check a PR ("review this PR", "pre-flight", "is this PR ready"), and as a self-check before handing off any PR. Routes each artifact in the diff to its canonical skill (commits, changesets, writing-tests, code-comments, pr-descriptions) and verifies the PR's claims empirically instead of stylistically.

Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests, Technical documentation and Verification before completion. The repository describes itself as: The Standalone Portable Text Editor. The licence is MIT.

When your agent uses it

  • Asked to review
  • Check a PR (review this PR
  • Is this PR ready)
  • As a self-check before handing off any PR

Example prompts

  • “review this PR”
  • “pre-flight”
  • “is this PR ready”
  • “/reviewing-prs”

What it can do on your machine

Read from SKILL.md and the folder at commit 60a494b. 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
    • 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

Reviewing PRs loads about 940 tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 490 words of instructions outside code blocks.

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

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 portabletext/editor at commit 60a494b, republished under its MIT licence (© portabletext). 490 words, ~940 tokens.

Download SKILL.mdSave it as .claude/skills/reviewing-prs/SKILL.md (or your agent's skills folder).
name
reviewing-prs
description
Review a PR in this repo against the house conventions before it is marked ready. Use when asked to review, pre-flight, or check a PR ("review this PR", "pre-flight", "is this PR ready"), and as a self-check before handing off any PR. Routes each artifact in the diff to its canonical skill (commits, changesets, writing-tests, code-comments, pr-descriptions) and verifies the PR's claims empirically instead of stylistically.

Reviewing PTE PRs

This skill owns the review procedure. The rules live in the canonical skills; read each one before auditing its artifact, and cite it in findings. Never restate a rule from memory: memory is how drift starts.

Gather

  • gh pr view <n> (title, body, draft state) and gh pr diff <n>.
  • git log origin/main..HEAD --format='%h %s' plus each commit's body.
  • Bucket the changed files: source, tests, .changeset/*.md, docs, config.

Route each artifact to its skill

Read the skill, then audit the artifact against it:

  • Commits → commits: subjects name the mechanism; a commit carrying a changeset is fix:/feat:; contract pins sit in their own test: commit while regression tests ride the fix; no ticket IDs anywhere; fixup! discipline once in review.
  • Changesets → changesets: present iff the change is user-facing; first line mirrors the commit subject verbatim; consumer-observable prose; secondary behavioral changes named explicitly.
  • Test files → writing-tests: canonical suite placement; every integration test is its own Scenario:; deterministic keys; full-value toEqual; no sleeps; no summarizer indirection; comments held to the source-file bar.
  • Comments in the diff → code-comments: default is no comment; why-only; nothing diff-relative; if the commit body already tells it, the comment is a duplicate and goes.
  • PR body → pr-descriptions: draft state, narrative shape, no internal context, behavioral changes volunteered, body sized to the diff.

Verify claims empirically

A stylistic pass is half a review. For every claim the PR makes, find the evidence or produce it:

  • A claimed regression test must be red pre-fix: check out the pre-fix source (or revert the fix hunks in the working tree) and run it, unless the PR or commit body records the red run.
  • Break something to trust something: prove at least one pinned test red by reverting or breaking the mechanism it claims to pin, even when the commit body records a red run. A review that broke nothing verified nothing empirically, and the strongest findings come from watching which tests do not notice a broken mechanism.
  • Run the gates the diff touches: check:types, check:lint, check:format, check:knip, and the affected package's test suites.
  • Spot-check "full value" assertions for smuggled partial matchers.
  • A named behavioral change must have a test proving the new behavior; an unnamed one found in the diff is a blocker, not a nit.
Show full SKILL.md (114 more words)Show less

Report

  • Findings ordered: blocker / should-fix / nit. Each names file:line, the rule (skill and section), and the concrete fix.
  • End with a verdict: ready to hand off, or the shortest list of changes that gets there.
  • When asked to fix rather than report, apply the findings and re-run the gates; history is rewritten (fold, not append) while the PR is a draft.

Anti-patterns

  • Rubber-stamping with a summary of the diff instead of an audit.
  • Restating skill rules from memory instead of reading the skill.
  • Style opinions not backed by a skill: raise them as questions, not findings.
  • Reviewing the investigation instead of the change: the diff, its commits, and its claims are the review surface.

© portabletext, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/reviewing-prs of portabletext/editor.

Open the folder on GitHubat commit 60a494b

Compare with similar skills

Reviewing PRs 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.

Reviewing PRs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Reviewing PRs this skillportabletext/editor280—~940Automated safety check: PassMIT
Post Draft Reviewagent-substrate/substrate4.6k—~2.8kAutomated safety check: PassApache-2.0
Review Kedro PRkedro-org/kedro11k—~2.8kAutomated safety check: PassCustom licence
Opik Documentation Patternscomet-ml/opik22k—~1.3kAutomated safety check: PassApache-2.0
Eli5coldteadotai/pr-lens1.9k—~2.3kAutomated safety check: PassMIT
Docs GuardamElnagdy/guard-skills1.3k—~2.1kAutomated safety check: PassMIT

Similar skills

  • Post Draft Review

    agent-substrate/substrate

    Posts pull request review findings as GitHub draft (pending) inline comments for a human to edit and submit, instead of publishing them straight to the PR author.

    4.6k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Review Kedro PR

    kedro-org/kedro

    Review a Kedro PR for checklist compliance, architecture, correctness, and clarity.

    11k GitHub stars~2.8k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Opik Documentation Patterns

    comet-ml/opik

    Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.

    22k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Eli5

    coldteadotai/pr-lens

    WHAT: Explains a codebase, a folder, a feature, a command or a pull request to someone who knows nothing about it, as a PR Lens canvas whose walkthrough builds the picture one part at a time.

    1.9k GitHub stars~2.3k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • Docs Guard

    amElnagdy/guard-skills

    Checks generated or edited documentation against the source code, flagging invented symbols, outdated samples and unverifiable claims before publishing.

    1.3k GitHub stars~2.1k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • Review PR

    javierbrea/eslint-plugin-boundaries

    Review a GitHub pull request from three perspectives — functional fit against its linked issue, code correctness/quality, and architectural boundaries — then post a single GitHub review: one general…

    997 GitHub stars~2.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from portabletext/editor

All 10 skills in this repo

  • Product Copy Assistant

    portabletext/editor

    Write clear, concise, accessible product copy for interfaces, docs, and system messages.

    280 GitHub stars~635 tokensUpdated today
    Auto-check passed

  • Changesets

    portabletext/editor

    How to write changesets in the Portable Text Editor monorepo.

    280 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Commits

    portabletext/editor

    How to write commit messages in the Portable Text Editor monorepo.

    280 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Next Branch

    portabletext/editor

    How the next prerelease branch for the upcoming editor major works in the Portable Text Editor monorepo.

    280 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Backporting

    portabletext/editor

    How to backport a fix from main to a maintenance branch (editor-v6.x, editor-v7.x) in the Portable Text Editor monorepo.

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

  • Code Comments

    portabletext/editor

    How to write and review code comments in the Portable Text Editor monorepo.

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

Categories

Questions about Reviewing PRs

What does Reviewing PRs do?

Review a PR in this repo against the house conventions before it is marked ready. Reviewing PRs is an agent skill from portabletext/editor. Review a PR in this repo against the house conventions before it is marked ready.

When should I use Reviewing PRs?

Reviewing PRs fits situations like: asked to review; check a PR (review this PR; is this PR ready); as a self-check before handing off any PR.

How do I install Reviewing PRs in Claude Code?

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

How do I install Reviewing PRs in Codex?

Run `npx skills add portabletext/editor --skill reviewing-prs -a codex`. Or copy the skill folder (.agents/skills/reviewing-prs in portabletext/editor) into .agents/skills/reviewing-prs in your project. Codex loads it when a task matches its description.

Can I use Reviewing PRs 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 portabletext/editor --skill reviewing-prs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reviewing-prs, .gemini/skills/reviewing-prs, .github/skills/reviewing-prs and .opencode/skills/reviewing-prs in your project.

What does Reviewing PRs need to run?

Going by SKILL.md and its folder, Reviewing PRs needs the command-line tools its instructions call (gh and git).

Does Reviewing PRs 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 Reviewing PRs 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 Reviewing PRs use?

Reviewing PRs 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 Reviewing PRs use?

About 940 tokens (SKILL.md is roughly 3.8k 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 Reviewing PRs?

Skills that share tags, products or a category with Reviewing PRs: Post Draft Review (agent-substrate/substrate, 4.6k stars), Review Kedro PR (kedro-org/kedro, 11k stars), Opik Documentation Patterns (comet-ml/opik, 22k stars) and Eli5 (coldteadotai/pr-lens, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Reviewing PRs?

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

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