pr-report

Analyze pull requests and branches into HTML or Markdown review reports.

3|Updated Apr 11, 2026

Search Tags:#architecture #diff #pr #tutorial #code-review #report #maintainer

Ready to run

npx skills add https://github.com/googlarz/stapler --skill pr-report-googlarz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-report
Source: https://github.com/googlarz/stapler/tree/main/.agents/skills/pr-report
Command: npx skills add https://github.com/googlarz/stapler --skill pr-report-googlarz

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Reviewers and maintainers often spend excessive time interpreting PRs; this skill provides a clear, tutorial-style analysis that explains design decisions and governance implications, reducing ambiguity and speeding up decisions.

Core Features & Use Cases

Tutorial-style PR analysis: explain the change as built, not just the diff, and highlight architectural considerations.
Executive summary and actionable outcomes: distill findings into a decision-ready narrative with concrete recommendations.
Output artifacts: produce standalone HTML or Markdown reports suitable for sharing with stakeholders.
Use cases: ideal for deep PR reviews, design comparisons, or merge recommendations across repositories.

Quick Start

Provide a PR URL or local branch to analyze and request a maintainer-grade report.

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 maintainer-grade PR review for a feature branch?▼

To generate a maintainer-grade PR review, provide a PR URL or local branch to analyze. The skill produces a tutorial-style walkthrough explaining design decisions and governance implications, outputting an executive summary with actionable recommendations.

What is a tutorial-style code review report and when do I need one?▼

A tutorial-style code review report explains the change as built, not just the diff, highlighting architectural considerations. You need one when interpreting large contributions or cross-repository changes to reduce ambiguity and speed up merge decisions.

Can I export PR analysis results as standalone HTML or Markdown reports?▼

Yes, you can export PR analysis results as standalone HTML or Markdown reports. These consumable artifacts are stored in the report/ or tmp/reports directories, making them suitable for sharing with stakeholders.

Does this PR review tool work with large contributions across multiple repositories?▼

Yes, this PR review tool works with large contributions across multiple repositories. It analyzes single PRs, feature branches, or large contributions, distilling architectural considerations into a decision-ready narrative.

What is the best way to analyze architectural design decisions in a pull request diff?▼

The best way to analyze architectural design decisions in a pull request diff is using an automated review skill that interprets the change as built. It highlights governance implications and provides concrete merge recommendations.

Why should I use an automated PR report instead of manually reviewing the diff?▼

You should use an automated PR report because reviewers often spend excessive time interpreting PRs. It provides a clear analysis explaining design decisions and governance implications, reducing ambiguity and speeding up decisions.