review-pr

Audit open GitHub pull requests and return structured read-only reviews.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/0xdeafcafe/skills --skill review-pr-0xdeafcafe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/0xdeafcafe/skills/tree/main/skills/review-pr
Command: npx skills add https://github.com/0xdeafcafe/skills --skill review-pr-0xdeafcafe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives you a thorough, read-only review of an open pull request when you want clear findings without editing files, pushing commits, or changing the PR itself. It is useful for getting an independent quality verdict on your own PR before fixing it, or auditing someone else's PR safely.

Core Features & Use Cases

  • Full-spectrum PR auditing: Reviews code quality, tests, feature behavior, security, UX, and spec alignment in one coordinated pass.
  • Adaptive review pipeline: Scales from small PRs to large, multi-slice changes by triaging diff size, faning out to specialist reviewers, and merging structured findings.
  • Read-only GitHub review output: Produces a terminal report by severity or posts findings as PR comments without approving, editing, resolving threads, or pushing changes.
  • Use Case: Before requesting formal team review, run this Skill on a large GitHub PR to surface logic bugs, missing tests, security risks, and cross-file contract issues in a structured report.

Quick Start

Ask the assistant to review PR #123 with the review-pr skill and return a read-only severity-ranked audit.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I get a read-only review of a GitHub pull request without modifying the code?

A read-only GitHub pull request review audits an open PR by number, URL, or branch and returns a structured report of problems, risks, and quality issues without editing files, pushing commits, or changing the PR itself. It surfaces logic bugs, missing tests, and security risks safely.

Can I audit a large GitHub pull request for security and test coverage automatically?

You can audit a large GitHub pull request by triaging the diff size, fanning out to specialist reviewers for security and test coverage, and merging structured findings into a severity-ranked report. This scales adaptively from small PRs to large multi-slice changes.

What's the best way to post inline review comments on a pull request without approving it?

Posting inline review comments without approving a pull request involves producing a read-only GitHub review output that posts findings as PR comments. It strictly avoids approving, editing, resolving threads, or pushing changes, providing an independent quality verdict safely.

Does this pull request analysis approach work with specific PR numbers and current branches?

Pull request analysis by PR number, URL, or current branch is fully supported for pre-merge checks. It retrieves the diff, enumerates files, triages by size, and optionally applies LSP-assisted structure analysis to assess cross-file contract issues.

What are the limitations of a read-only code review for a pull request?

A read-only code review for a pull request is limited to non-editing GitHub operations and cannot fix files, push commits, or resolve threads. It functions strictly as an independent auditing tool to surface quality issues rather than an automated remediation pipeline.