pr-review

Reviews GitHub pull requests and posts pending reviews with inline comments.

Updated May 11, 2026
One-click install
npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill pr-review-thachrocky12345
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/thachrocky12345/local-agent-train-workstation/tree/main/qvac/.cursor/skills/pr-review
Command: npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill pr-review-thachrocky12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing pull requests thoroughly requires checking gitflow rules, CI status, title and body format, code quality, and security, which is time-consuming and error-prone when done manually. ## Core Features & Use Cases - Deep PR Analysis: Validates gitflow direction, CI check results, PR title/body format against repo rules, and reviews code for bugs, security issues, and breaking changes. - Severity-Tiered Findings: Classifies findings as High, Medium, or Low, presents a chat overview with code excerpts and deep links, and lets the user pick which findings become inline comments. - Safe Pending Reviews: Posts a PENDING GitHub review with per-file:line inline comments only after explicit user confirmation, without ever touching the user's local working tree. - Use Case: Given a PR URL like https://github.com/tetherto/qvac/pull/1234, the skill fetches the diff in an isolated worktree, reviews it against applicable cursor rules, and drafts inline comments for the user to approve and submit. ## Quick Start Ask the assistant to review a pull request by providing its GitHub URL, for example by invoking /pr-review with the PR link.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I review a GitHub pull request with inline comments?

Provide the PR URL or invoke /pr-review with the link. The skill fetches the PR metadata and diff, analyzes the changes, shows a severity-tiered overview in chat, and lets you select which findings become inline comments in a pending review.

What does an automated PR review check before posting comments?

It validates gitflow merge direction, CI check status, PR title and body format against repo rules, and reviews code for bugs, security issues, breaking changes, and missing test coverage. Findings are classified as High, Medium, or Low severity.

Does the PR review skill modify my local git working tree?

No, the skill is strictly read-only with respect to your working tree. It uses an isolated git worktree under ~/.cache/qvac-pr-review at the PR head SHA, and forbids commands like git checkout, reset, stash, or gh pr checkout in your repo.

Can I control which review findings get posted as inline comments?

Yes, after the chat overview you confirm exactly which findings to include. High and Medium findings are pre-selected by default, Low findings are opt-in, and nothing is posted until you approve the final gh api command.

Why does the posted review stay in PENDING state on GitHub?

The payload omits the event field, which the GitHub REST API interprets as a pending review rather than an approval or change request. You submit the review manually from the GitHub UI after inspecting the inline comments.