review-pr

Automate GitHub pull request reviews with inline comments.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/NooBat/claude --skill review-pr-noobat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/NooBat/claude/tree/main/skills/review-pr
Command: npx skills add https://github.com/NooBat/claude --skill review-pr-noobat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the GitHub PR review workflow by dispatching a code-reviewer subagent, reading changed files, and posting a structured review with inline line-range comments to GitHub.

Core Features & Use Cases

  • Dispatch the superpowers:code-reviewer subagent to review a GitHub PR.
  • Read changed files and gather PR context (title, body, base/head refs, files changed, author).
  • Post a structured review back to GitHub with inline file comments (including line ranges) and a general review body.
  • Announce at start to inform observers and ensure deterministic worktree handling by using a separate temporary worktree path for reads.
  • Create a temporary worktree at the PR's HEAD (without touching the main worktree) and read files from that path.

Quick Start

Activate the review-pr skill by supplying a PR number to trigger an automated code-review and publish a structured inline-comment review to GitHub.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate GitHub pull request reviews with inline code comments?

Automate GitHub pull request reviews by dispatching a code-reviewer subagent that reads changed files and posts a structured review with inline line-range comments directly to GitHub. The skill uses PR metadata and diffs to generate feedback without manual reading.

Does automated PR review require a separate worktree to read repository files?

Automated PR review uses a temporary worktree at the PR's HEAD to read files, ensuring deterministic handling without touching the main worktree. This separate path allows the code-reviewer subagent to safely access the full repository state.

Can I post inline review comments on specific line ranges in a GitHub PR?

Posting inline review comments on specific line ranges in a GitHub PR is supported by this skill. It analyzes the changed files, constructs a structured review with precise line-range comments, and publishes the complete feedback back to the GitHub repository.

What PR metadata is needed to trigger an automated code review on GitHub?

Triggering an automated code review on GitHub requires the PR number, HEAD_SHA, BASE_SHA, and repository context. This metadata allows the skill to gather the title, body, base and head refs, and the files changed to perform the review.

How to review changed files in a pull request without modifying the main working directory?

Reviewing changed files without modifying the main working directory is achieved by creating a temporary worktree at the PR's HEAD. The skill reads the full repository state from this isolated path, dispatches the code-reviewer, and leaves the main worktree untouched.