pr-review-sweep

Analyze and act on GitHub PR review comments with post-merge follow-ups.

1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielraffel/burl --skill pr-review-sweep-danielraffel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-sweep
Source: https://github.com/danielraffel/burl/tree/main/.agents/skills/pr-review-sweep
Command: npx skills add https://github.com/danielraffel/burl --skill pr-review-sweep-danielraffel

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps address the challenge of managing and acting on automated and human review comments for PRs, ensuring high-quality code reviews.

Core Features & Use Cases

  • Automated & Human Review Comments Analysis: Sweep through both automated and human reviews to identify and prioritize issues.
  • Material PRs Handling: Specifically designed for PRs involving significant changes to critical code paths, reducing the risk of critical issues going unnoticed.
  • Post-Merge Follow-ups: Facilitates follow-up on reviews even after a PR has been merged, ensuring ongoing quality control.

Quick Start

Use pr-review-sweep <pr_number> to initiate the PR review sweep for the specified pull request number.

Frequently Asked Questions about pr-review-sweep

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

FAQPage Schema
How do I systematically review GitHub PR comments for material code changes?

To systematically review GitHub PR comments, you can sweep through both automated and human reviews to identify and prioritize issues involving significant changes to critical code paths. This approach reduces the risk of critical issues going unnoticed.

Can I follow up on automated code review comments after a PR is merged?

Yes, you can follow up on automated code review comments after a PR is merged. This ensures ongoing quality control by handling comments asynchronously and providing mechanisms for post-merge follow-ups on material code changes.

Do I need the gh CLI to analyze pull request comments asynchronously?

Yes, you need the gh CLI and ghapp dependencies to analyze pull request comments asynchronously. These tools provide the necessary GitHub integration to access PR data and process automated and human review comments effectively.

What is the best way to manage post-merge follow-ups for critical code paths?

The best way to manage post-merge follow-ups for critical code paths is to systematically sweep PR comments asynchronously. This handles both automated and human reviews, prioritizing material changes to ensure high-quality code reviews and ongoing quality control.

How do I start a PR review sweep for a specific pull request?

To start a PR review sweep, use the command `pr-review-sweep <pr_number>` with your specified pull request number. This initiates the analysis of both automated and human review comments for that PR.