review

Resolve branches or PRs and generate structured code review findings.

1|4|Updated Oct 27, 2014
One-click install
npx skills add https://github.com/rjernst/dotfiles --skill review-rjernst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/rjernst/dotfiles/tree/main/claude/skills/review
Command: npx skills add https://github.com/rjernst/dotfiles --skill review-rjernst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review code changes on the current branch, a different branch, or a pull request by guiding workspace setup and producing structured findings you can act on.

Core Features & Use Cases

  • Branch/PR resolution: Accepts no input, a PR number/URL, or natural-language branch intent and resolves it to a concrete target branch.
  • Workspace-first safety: Enforces that reviews only happen in the correct worktree, creating an isolated review workspace when needed.
  • Structured review output: Produces consistent sections for Critical, Suggestions, and Good, plus a clear verdict and next-step prompts.

Quick Start

Use the review skill by invoking /review while on the target branch to generate a structured code review of the changes relative to main (or the PR base branch).

Frequently Asked Questions about review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a semantic code review on a git pull request?

Semantic code review on a pull request resolves the target branch, inspects diffs and history, and generates structured findings categorized into Critical, Suggestions, and Good sections with a final merge verdict.

How do I review code changes on a branch without affecting my current workspace?

Reviewing code changes safely requires creating an isolated review workspace or worktree, ensuring your current working directory remains untouched while diff analysis and security checks run against the target branch.

Can I use natural language to specify which branch I want to review?

Yes, branch resolution accepts natural-language branch intent, a specific PR number, a URL, or no input to automatically resolve and select the correct review target branch for analysis.

What is included in the structured output of a branch diff analysis?

Branch diff analysis output includes structured sections for Critical issues, Suggestions, and Good practices, followed by a clear merge verdict and actionable next-step prompts for the developer.

Does this code review workflow prepare comments directly on a GitHub pull request?

Yes, when requested, the code review workflow uses GitHub PR tooling to optionally prepare PR comments based on the structured findings gathered during the semantic diff analysis.

What are the limitations of using worktree safety checks for branch reviews?

Worktree safety checks enforce that reviews only happen in the correct worktree by creating an isolated workspace, meaning you cannot bypass workspace creation rules when running a branch review.