review-pr

Reviews pull requests and branch diffs, producing a structured REVIEW_PR.md with findings and merge recommendation.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/truongnat/Restly --skill review-pr-truongnat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/truongnat/Restly/tree/main/.agents/skills/review-pr
Command: npx skills add https://github.com/truongnat/Restly --skill review-pr-truongnat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing pull requests consistently is hard: reviewers skip verification, miss security risks, or disturb their own working tree while inspecting someone else's branch. This Skill enforces a hard review contract that produces an evidence-based review artifact before merge. ## Core Features & Use Cases - Safe diff inspection: Defaults to remote-diff mode using three-dot git diff (base...head) so the current branch and uncommitted work are never touched; escalates to an isolated external worktree only when runtime verification is needed. - Structured findings: Every finding carries severity (Critical/High/Medium/Low/Info), location, evidence, impact, recommendation, and confidence, plus testing gaps and residual risks. - Merge recommendation taxonomy: Outputs Approve, Approve with comments, Request changes, Needs more info, Needs more verification, or Blocked, with PR description accuracy checked against the actual diff. - Use Case: A teammate opens a PR from branch A into develop. You ask the agent to review it; it fetches refs, diffs origin/develop...origin/A, checks CI status via gh, and writes REVIEW_PR.md with findings and a merge recommendation — without checking out anything. ## Quick Start Ask the agent to review the pull request from branch feature-x into develop and produce the REVIEW_PR.md report with findings and a merge recommendation.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I review a pull request without checking out the branch?▼

Use remote-diff mode: run git fetch origin, then git diff --find-renames base...head with three-dot notation. This scopes the diff to changes since the merge-base without touching your current branch or working tree.

How to review a PR when I need to run tests on the head branch?▼

Create a detached git worktree outside the repository with git worktree add --detach, then run the project's test and build commands there. Remove the worktree afterward without --force, and never edit .gitignore during review.

Can this review skill approve or merge a pull request automatically?▼

No. The skill never approves on behalf of the user, never auto-fixes the PR, and never claims merge-safe without verification evidence. It only produces a merge recommendation such as Approve, Request changes, or Needs more verification.

What should a code review report include before merging?▼

A review report should include base and head refs, review mode, findings with severity and evidence, verification results, testing gaps, residual risks, PR description accuracy, and a merge recommendation. This skill writes all of these into REVIEW_PR.md.

What are the limitations of diff-based pull request review?▼

Diff-only review cannot run tests locally, so runtime checks are marked skipped and CI evidence is used instead. It also does not replace a deep security audit and cannot guarantee finding all bugs when evidence is insufficient.