Index of every page on this site: llms.txt
All skills
vercel avatar

/review-pr

@86694bd
by vercelvercel/board147 stars
13
Run it yourself

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.

  • 1 file
  • 1.6 KB
  • Updated 4 days ago
  • GitHub
Use this Skill: https://skilld.dev/gh/vercel/board/review-pr

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈59 tokens for metadata: the name and description. ≈344 when used: this file.

Description uses 3.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈237 characters, or 3.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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:

    {
      "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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 86694bd. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 12 hours ago.

Activeupdated 4 days ago

README badge

README badge for vercel/board/review-pr