github-review-publisher

Generate pending GitHub PR review comments with severity-based styling.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/maverox/claude-plugins --skill github-review-publisher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-review-publisher
Source: https://github.com/maverox/claude-plugins/tree/main/plugins/connector-integration-suite/skills/github-review-publisher
Command: npx skills add https://github.com/maverox/claude-plugins --skill github-review-publisher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub PR reviews are time-consuming and error-prone when translating upstream quality signals into actionable inline comments. This skill automates the generation and formatting of GitHub PR review comments with line-level precision, producing structured, severity-categorized notes and publishing them as pending reviews for later manual approval.

Core Features & Use Cases

  • Auto-format issues into GitHub review comments with severity-based styling.
  • Aggregate issues from multiple upstream skills (code-quality-review and connector-integration-validator) and deduplicate.
  • Group comments by file for easy review and support multi-file reviews.
  • Create pending reviews via GitHub API to allow manual approval before posting.

Quick Start

Provide upstream issues data and run the skill to generate a pending GitHub PR review with inline comments.

Frequently Asked Questions about github-review-publisher

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

FAQPage Schema
How do I automate GitHub PR review comments with inline code precision?

Automating GitHub PR review comments involves aggregating upstream issues and formatting them into line-level inline comments. This skill generates structured, severity-categorized notes and publishes them as a pending review for manual approval.

Can I aggregate code review issues from multiple sources into a single GitHub review?

Yes, you can aggregate code review issues from multiple upstream skills into a single GitHub review. The process deduplicates overlapping findings and groups comments by file to support multi-file PR reviews.

Does this approach support pending reviews for manual approval before posting to GitHub?

Pending reviews are supported via the GitHub API to allow manual approval before posting. This ensures reviewers can validate severity-based styling and inline guidance before the comments are publicly visible on the pull request.

How do I format code review issues with severity-based styling for GitHub?

Formatting code review issues with severity-based styling requires structuring upstream quality signals into categorized notes. The system translates these aggregated issues into formatted inline comments grouped by file for easy reviewer navigation.

Do I need the gh CLI to publish pending PR reviews with inline comments?

The gh CLI workflow is required to integrate with GitHub and publish pending PR reviews. It facilitates the generation and formatting of line-level comments and creates the pending review via the GitHub API.