pr-review

Name: pr-review
Availability: InStock
Author: gittower

Create a structured GitHub pull request review draft with inline comments.

413|31|Updated Mar 16, 2025

Search Tags:#diff analysis #code review #pull request #github #inline comments #review draft

Ready to run

npx skills add https://github.com/gittower/git-flow-next --skill pr-review-gittower

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/pr-review
Command: npx skills add https://github.com/gittower/git-flow-next --skill pr-review-gittower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you prepare a GitHub pull request review with clear summary feedback and precise inline comments without posting anything automatically, reducing the risk of sending incomplete or incorrect feedback.

Core Features & Use Cases

PR Inspection: Collects PR metadata, diffs, and commit history for a review-ready view of the change.
Review Drafting: Produces a structured review file with must-fix, should-fix, and nit items plus inline comments mapped to diff lines.
Safe Preview Workflow: Writes the review to disk first so you can inspect and edit it before submission.
Use Case: A maintainer can ask for a PR review, inspect the generated markdown file, and only submit it after confirming the tone, findings, and line comments are correct.

Quick Start

Ask the skill to review pull request 74 and write the draft review file to a preview folder.

Frequently Asked Questions about pr-review

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

FAQPage Schema

How do I draft a GitHub pull request review without posting it immediately?▼

You can create a structured pull request review draft by generating a markdown file with summary findings and inline comments written safely to disk, allowing you to inspect and edit feedback before submission.

How do I write inline comments mapped to specific diff lines in a code review?▼

Writing inline comments mapped to diff lines requires parsing the pull request diff and file metadata, then generating line-accurate feedback that aligns with the exact modified code blocks before submission.

What is the best way to classify review severity for pull request findings?▼

Pull request review severity classification categorizes findings into must-fix, should-fix, and nit items, producing a structured review draft that prioritizes code feedback by impact before posting.

Can I preview GitHub PR reviews before submitting them to maintainers?▼

Yes, a safe preview workflow writes the generated review draft to a local file first, so you can verify tone, findings, and line comments before submitting the review to GitHub.

Does pull request diff analysis require commit history context?▼

Pull request diff analysis benefits from retrieving commit history and PR metadata, providing a review-ready view of the change that adds necessary context for accurate inline feedback.

What are the limitations of generating a pull request review draft file?▼

A review draft file does not automatically post feedback to GitHub; it only writes the structured review to disk, requiring you to manually inspect and submit the final inline comments and summary.