pr-review-batching

Batch PR review comments into a pending GitHub draft review.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/dgowrie/claude-workflows --skill pr-review-batching
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-batching
Source: https://github.com/dgowrie/claude-workflows/tree/main/skills/pr-review-batching
Command: npx skills add https://github.com/dgowrie/claude-workflows --skill pr-review-batching

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stages PR review comments as drafts on a GitHub pending review; never publishes. Owns two operations: (1) ensure-then-append, which adds comments to an existing pending review or creates one if none exists, without clobbering user-in-flight edits; (2) incident response, which undoes an accidentally published review by deleting its visible comments and recreating as pending.

ACTION-BOUNDARY TRIGGER: consult this skill before any gh pr review invocation or any POST / DELETE on /pulls/{n}/reviews. This skill is the guard against publishing a review when the user wanted drafts. Also triggers on phrases: "draft comment", "pending review", "post this as a draft", "add to the review", "stage as a draft", or explicit /pr-review-batching.

Core Features & Use Cases

  • Stage comments by batching them into a single pending review, ensuring drafts remain draft until user confirmation.
  • Append to an existing pending review or create a new pending review when none exists, preserving user edits.
  • Quickly recover from accidental publishes by performing incident response to delete visible inline comments and recreate as a pending review.

Quick Start

Batch your draft PR comments into a pending review for the target PR.

Frequently Asked Questions about pr-review-batching

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

FAQPage Schema
How do I batch GitHub PR review comments into a draft instead of publishing them?

Batch GitHub PR review comments into a pending draft by using the ensure-then-append operation, which adds comments to an existing pending review or creates one without clobbering in-flight edits. This keeps drafts unpublished until confirmation.

How do I undo an accidentally published GitHub pull request review?

To undo an accidentally published pull request review, use the incident response operation which deletes visible inline comments and recreates them as a pending GitHub draft review. This restores your unpublished staging state.

What is a pending GitHub PR review and when do I need it?

A pending GitHub PR review is an unpublished draft state that batches inline comments without submitting them. You need it when staging feedback over time to prevent accidental publication before final review confirmation.

Can I append new comments to an existing draft pull request review without losing my edits?

Yes, you can append new comments to an existing draft pull request review without losing user-in-flight edits. The ensure-then-append protocol preserves current pending review state while safely adding new staged comments.

What are the limitations of using pending reviews to stage PR comments?

Limitations of staging PR comments as pending reviews include strict race-window protocols and safety checks required to prevent conflicts. It relies on specific GitHub REST and GraphQL endpoints to reconstruct drafts without corrupting concurrent edits.