---
name: review-pr
description: "Review someone's pull request: check it out, read and run it, try the change, and submit one GitHub review. Use when a thread is a pull request (its root is labeled pr=<owner/repo>#<N>), and again when new commits land on it."
title: review-pr
canonical_url: https://skilld.dev/gh/vercel/board/review-pr
last_updated: 2026-11-19T06:15:42.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install vercel/board/review-pr`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/review-pr`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/vercel/board/review-pr) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/review-pr`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/review-pr --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/review-pr --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Review a pull request

The thread's root is labeled `pr=<owner/repo>#<N>`. Your own PRs never come in as threads, so a
PR here is someone else's.

1. **Check it out and read it.** `gh pr checkout <N> --repo <owner/repo>`, then read the diff
   (`gh pr diff <N> --repo <owner/repo>`), the PR's description, and the repo's AGENTS.md or
   README for the parts it touches.
2. **Run it.** Install and run the checks the repo uses, and the tests nearest the change.
3. **Try it.** Where you can, use the change the way a person would: run the CLI, hit the route,
   or open the page in the browser (the ui-demo skill shows how to run a dev server).
4. **Review once, on GitHub.** Write `review.json` and submit it with
   `gh api repos/<owner/repo>/pulls/<N>/reviews --input review.json`:

   ```json
   {
     "event": "COMMENT",
     "body": "The verdict, in a line or two.",
     "comments": [{ "path": "src/file.ts", "line": 42, "body": "What's wrong here and why." }]
   }
   ```

   `event` is `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. Comments go on lines the diff touches.
   Say what's wrong and why, and what would fix it; leave out what's fine.

The review reaches the board thread on its own, so don't restate it there. When new commits land
(`gh pr view <N> --repo <owner/repo> --json commits`), review again: what changed, and whether it
settles what you raised.
