prrr

Automate GitHub PR reviews by collecting context, drafting prioritized comments, and publishing.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/eugene-belkovich/ai-setup --skill prrr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prrr
Source: https://github.com/eugene-belkovich/ai-setup/tree/main/codex/profiles/work/skills/workflow/prrr
Command: npx skills add https://github.com/eugene-belkovich/ai-setup --skill prrr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

Automates remote GitHub PR reviews by collecting context, drafting prioritized feedback, and publishing the review on GitHub.

Core Features & Use Cases

  • Reads prior reviews and inline comments to avoid duplicates.
  • Drafts up to four prioritized review comments based on context.
  • Publishes the final review to GitHub, providing a reproducible audit trail.
  • Supports inputs via PR URL, repo/name + PR number, or the current local branch PR.

Quick Start

Run the collector to gather PR context and then publish the review for the target PR.

Frequently Asked Questions about prrr

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

FAQPage Schema
How do I automate GitHub PR reviews and publish feedback automatically?▼

Automating GitHub PR reviews involves collecting repository context, drafting prioritized feedback, and publishing the final review to GitHub. This skill reads prior inline comments to avoid duplicates and supports inputs via PR URL or current branch.

What's the best way to avoid duplicate comments in automated code review?▼

To avoid duplicate comments in automated code review, the system reads existing reviews and inline comments before drafting new feedback. It then generates up to four prioritized comments to ensure the published review adds unique value.

How do I run an automated PR review using GitHub CLI?▼

Running an automated PR review with GitHub CLI requires the bundled collect_pr_context.sh script to gather PR context. After collection, the system drafts feedback and publishes the final review to GitHub using the gh command.

Can I review a pull request using my current local branch?▼

Yes, you can review a pull request using your current local branch. The automation supports multiple input methods, allowing you to target a PR by providing a URL, a repository and PR number, or your current local branch.

Do I need jq installed to automate publishing GitHub PR reviews?▼

Yes, you need jq installed to automate publishing GitHub PR reviews. The skill relies on both the GitHub CLI and jq as dependencies to collect context, parse data, and publish the final review artifacts.

What limitations exist when drafting automated PR review comments?▼

A limitation when drafting automated PR review comments is that the system generates a maximum of four prioritized comments per review. It also applies primarily to PRs across repositories where existing reviews are already present.