pdd-pr-review

Summarize GitHub and local PR review results into structured merge recommendations.

13|3|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill pdd-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pdd-pr-review
Source: https://github.com/wonderslife/pdd-skills-v3/tree/main/skills/pr/pdd-pr-review
Command: npx skills add https://github.com/wonderslife/pdd-skills-v3 --skill pdd-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR review data is often scattered across comments, checks, and reports. This Skill consolidates review results and provides clear, actionable guidance for merge decisions.

Core Features & Use Cases

  • Aggregation of review signals: blocking, warning, and suggestion counts are summarized into a single view.
  • Multi-mode operation: supports both GitHub-based PR workflows and local PR records for offline contexts.
  • Use Case: when a PR receives mixed feedback, quickly determine whether to merge, request fixes, or reopen.

Quick Start

Analyze the current PR and present a concise decision with recommended actions.

Frequently Asked Questions about pdd-pr-review

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

FAQPage Schema
How do I consolidate GitHub PR review comments and status checks into a single merge decision?

To consolidate GitHub PR review data, this Skill aggregates blocking, warning, and suggestion counts from status checks and comments, outputting a structured report with actionable merge recommendations.

Can I analyze local PR records for offline code review without connecting to the GitHub API?

Yes, you can analyze local PR records offline. This Skill supports multi-mode operation, allowing it to read local pull request data and generate merge recommendations without needing a live GitHub API connection.

What is the best way to summarize mixed PR feedback to determine if I should merge or request fixes?

The best way to summarize mixed PR feedback is to aggregate review signals into blocking, warning, and suggestion categories, which provides a concise decision on whether to merge, request fixes, or reopen.

How do I generate a structured review report that links change-id to pull request status?

You can generate a structured review report by reading PR data and linking change-id information. The Skill handles this linkage and outputs a structured report summarizing the aggregated review results.

What should I do when my pull request has mixed feedback and I am unsure whether to reopen it?

When a pull request has mixed feedback, you should aggregate the review signals to count blocking issues, warnings, and suggestions, which will provide clear actionable guidance on whether to reopen.