Github Review
Review a GitHub pull request — the PR-review behavior that used to live in the built-in `/review`, split out now that `/review` is the review orchestrator. Fetches the PR with `gh`, reviews the diff at an evidence-graded bar (only a fully-traced finding is blocking), and optionally posts inline PR comments. For your uncommitted working diff use `/review` instead; this command is specifically for a PR. Triggers on `/github-review`, `/github-review <pr>`, "review this pull request", "review PR #N".
Install
npx skills add iamneilroberts/claude-skills --skill github-reviewgit clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/github-review ~/.claude/skills/github-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# /github-review — review a GitHub pull request
Reviews a **GitHub pull request** (the behavior the built-in `/review` used to provide, now that
`/review` is the review orchestrator). For your *uncommitted working diff*, use `/review` (it
picks the right shape) or a direct code-review — this command is specifically for a PR.
Usage: `/github-review [<pr-number-or-url>] [focus aspects…]`. With no argument, target the PR for
the current branch (`gh pr view --json number`), or ask which PR if there isn't one.
## Steps
1. **Fetch the PR.** `gh pr view <pr> --json number,title,body,headRefName,baseRefName,additions,deletions,files`
and `gh pr diff <pr>`. If `gh` isn't authenticated, say so and stop.
2. **Review the diff at the evidence bar** (same ladder as `/review`'s light mode):
- **CONFIRMED** — full traced path (file:line → file:line, 3+ steps) or a concrete triggering
input. Only CONFIRMED is blocking.
- **LIKELY** — strong reasoning, one inferred link. **POSSIBLE** — a smell, untraced,
informational. **UNFOUNDED** — ruled out.
- Verify assumptions first: does the change actually wire in (a new/edited unit is registered/
imported where the system loads it, new config/env is declared where the code reads it), are
public names/routes/stored-data keys stable, is every write path updated for a new stored field.
- Domain checks: schema/API consistency across consumers, concurrency (unguardedDetails
- Skill name
github-review- Repository
- iamneilroberts/claude-skills
- Path
skills/github-review/SKILL.md- Repo updated
- 21 August 2026
FAQ
What does the Github Review skill do?
Review a GitHub pull request — the PR-review behavior that used to live in the built-in `/review`, split out now that `/review` is the review orchestrator. Fetches the PR with `gh`, reviews the diff at an evidence-graded bar (only a fully-traced finding is blocking), and optionally posts inline PR comments. For your uncommitted working diff use `/review` instead; this command is specifically for a PR. Triggers on `/github-review`, `/github-review <pr>`, "review this pull request", "review PR #N".
How do I install the Github Review skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill github-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Github Review popular?
It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.
Related skills
Brag
37iamneilroberts/claude-skills
Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write
Branch
37iamneilroberts/claude-skills
Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".
Claude Code Best Practices
37iamneilroberts/claude-skills
Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.
Idea
37iamneilroberts/claude-skills
Capture a fix / feature / research idea fast and turn it into a tracked GitHub Issue plus a lightweight planning doc, so nothing gets lost and it shows up next time you list your issues. Runs a short confirm-or-edit interview (infers title/slug/type from your one-liner, you accept or correct), writes docs/ideas/<date>-<slug>.md, files a labelled GitHub Issue via gh, and backlinks the issue URL into the doc. Triggers on `/idea <one-liner>`, `/idea`, "capture this idea", "file an idea", "log a thing to fix/build/research", "remember to look into X".
Fix Issue
37iamneilroberts/claude-skills
Take a GitHub issue and actually resolve it end to end — read the issue, reproduce it, fix it in an isolated branch with a test, verify, and open a PR that closes the issue. The counterpart to /idea (which files issues): /idea captures, /fix-issue clears. Works off `gh` in whatever repo you're in. Triggers on `/fix-issue <number|url>`, "fix issue #N", "resolve this github issue", "pick up and fix issue N".
Pickup
37iamneilroberts/claude-skills
Use when the user wants to pick up / resume the most recent handoff in an isolated worktree — finds the newest handoff doc, RESUMES the worktree/branch it documents if one exists (re-adding it if parked), otherwise creates a fresh branch + worktree, then loads the handoff's context so work continues where it left off. Triggers on `/pickup`, "pick up the handoff", "resume the latest handoff in a worktree", "branch and continue". Distinct from `session-resume` (loads a handoff in-place, never branches) and `branch` (makes a worktree, loads no handoff) — `/pickup` does both, reusing an existing w
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.