post-pr-review

Publish consolidated GitHub pull request reviews in a single API call.

1|Updated May 2, 2026
One-click install
npx skills add https://github.com/abeyuya/skills --skill post-pr-review-abeyuya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-pr-review
Source: https://github.com/abeyuya/skills/tree/main/plugins/pr-review/skills/post-pr-review
Command: npx skills add https://github.com/abeyuya/skills --skill post-pr-review-abeyuya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews that rely on multiple incremental comments are slow and can leave the PR in an inconsistent state, so this skill standardizes publishing one consolidated GitHub PR review.

Core Features & Use Cases

  • One-call consolidated PR Review posting: Submits the entire review (summary + inline annotations) as a single GitHub review API call.
  • Safe event constraints: Always posts with event type COMMENT to avoid approval/blocking behaviors.
  • Structured inline review annotations: Supports both single-line and multi-line inline comment ranges with side and line positioning.

Quick Start

Tell the agent to call post-pr-review with OWNER, REPO, PR_NUMBER, an overall markdown body, and a list of inline comments to publish the PR review as one consolidated review.

Frequently Asked Questions about post-pr-review

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

FAQPage Schema
How do I post a consolidated GitHub pull request review with inline comments in one API call?

To post a consolidated GitHub pull request review, construct a single payload to the /repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/reviews endpoint containing the markdown body and inline annotations. This avoids fragmented multi-step posting and prevents inconsistent PR states.

Why does my automated pull request review workflow leave the PR in an inconsistent state?

Pull request review workflows that rely on multiple incremental comments can leave the PR in an inconsistent state because API calls may fail midway. Posting one consolidated review with a single API call standardizes the process and ensures atomic submission.

Can I approve a pull request or request changes using the GitHub reviews API with this automation?

No, you cannot approve or request changes. This approach strictly requires a fixed COMMENT event type for the pull request review, intentionally rejecting approve or request-changes usage to avoid automated approval and blocking behaviors.

How do I add multi-line inline comments to a GitHub pull request review payload?

To add multi-line inline comments to a GitHub pull request review, structure the annotations with side and line positioning parameters. The payload supports both single-line and multi-line ranges to annotate specific code sections within the review.

Do I need a specific commit ID to post inline annotations on a pull request?

A specific commit ID is optional when posting inline annotations. You can construct the pull request reviews payload with an optional commit_id parameter to target the exact code state for your single-line or multi-line inline comments.

What is the best way to automate publishing PR review summaries without fragmenting comments?

The best way to automate publishing PR review summaries is submitting the entire review, including the markdown body and inline annotations, as a single GitHub API call. This prevents fragmented multi-step posting and guarantees consistent review state.