pr-report

Review pull requests and generate maintainer-ready HTML or Markdown reports.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/kangnam7654/stapler --skill pr-report-kangnam7654
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-report
Source: https://github.com/kangnam7654/stapler/tree/main/.agents/skills/pr-report
Command: npx skills add https://github.com/kangnam7654/stapler --skill pr-report-kangnam7654

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Review a pull request deeply to produce a maintainer-friendly report.

Core Features & Use Cases

  • Explain the design decisions and code changes in the PR with tutorial-style clarity.
  • Compare the PR to similar system designs and provide a concrete merge recommendation.
  • Produce polished artifacts (HTML or Markdown) and a concise maintainer summary.

Quick Start

Generate a maintainer-grade PR review report from the target branch or diff, including rationale and recommended actions.

Frequently Asked Questions about pr-report

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

FAQPage Schema
How do I generate a PR review report for a large branch contribution?

To generate a PR review report, input the target branch or diff to produce a maintainer-ready artifact such as HTML or Markdown, complete with tutorial-style explanations and merge recommendations.

Can I compare a pull request to similar system designs before merging?

Yes, PR review reports compare the pull request to similar system designs, explaining design decisions and providing a concrete merge recommendation to guide maintainers before integration.

What is a maintainer-friendly PR review brief?

A maintainer-friendly PR review brief is an artifact that explains code changes with tutorial-style clarity, compares alternatives, and delivers explicit merge recommendations for codebase maintainers.

Does the PR review report work for branches without an active pull request?

Yes, the review process is applicable to PRs, branches, or large contributions across codebases, allowing you to analyze design decisions and prepare merge recommendations independently.

What format is the PR review report output in?

The PR review report is produced as a polished artifact in either HTML or Markdown format, including a concise maintainer summary and explicit merge recommendations.

When do I need an automated PR review report?

You need an automated PR review report when evaluating large contributions across codebases, requiring deep design analysis, alternative comparisons, and a maintainer-ready summary to guide merge decisions.