# Review Pull Request

Judges a pasted GitHub PR for security and runtime safety with a merge recommendation.

- Repository: https://github.com/blackboardsh/electrobun (12996 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add blackboardsh/electrobun --skill review-pr -g -a claude-code -y`
Codex: `npx skills add blackboardsh/electrobun --skill review-pr -g -a codex -y`
Cursor: `npx skills add blackboardsh/electrobun --skill review-pr -g -a cursor -y`
Gemini CLI: `npx skills add blackboardsh/electrobun --skill review-pr -g -a gemini-cli -y`

## Description

Review a GitHub pull request from its link, read the PR description, inspect the code locally only when useful, and judge whether the change is safe to run from a security and runtime-safety perspective. Use only after the user pastes a PR URL. Handle one PR at a time, make a clear merge/close/supersede recommendation, and keep all GitHub review and merge actions with the user.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Review PR

## Overview

Use this skill when the user pastes a PR link and wants a security-first assessment before running, testing, or merging it. The goal is to understand the PR intent, inspect the diff, decide whether it is safe to run, and then help with feedback, fixes, merge readiness, or a close recommendation.

This skill is discussion-first, but it should still support fast maintainer throughput. Loading the skill does not authorize guessing which PR to inspect from local branches, refs, or open worktrees. Wait for the user to paste a PR URL, review that one PR, give a concise rundown, and discuss it with the user before taking any local git actions beyond basic repository state checks.

If the maintainer is clearly trying to fly through PRs, keep the discussion short and move quickly to a decisive recommendation:

- `Merge`
- `Close`
- `Supersede with direct fix`

Use `Supersede with direct fix` when the underlying issue is legitimate but the PR implementation is too broad, changes the wrong behavior, or is close but not quite right. In that case, offer to implement the narrower fix locally and draft the close comment for the maintainer.

## Workflow

### 0. Wait for the PR URL

- Do not infer the target PR from local branches such as `pr-*`, from recent git history, or from the current worktree.
- Review one PR at a time, in the order the user pastes them.
- If no PR URL has been pasted in the current discussion, ask for it and stop there.
- After the user pastes a PR URL, read it first and respond with a rundown before fetching refs, checking out branches, or diffing local PR branches.

### 1. Read the PR first

The rest: https://github.com/blackboardsh/electrobun/blob/HEAD/.skills/review-pr/SKILL.md