pr-report

Name: pr-report
Availability: InStock
Author: mighty-hq

Generate a maintainer-grade review report for a pull request with merge recommendation.

Updated Mar 15, 2026

Search Tags:#code review #pull request #HTML report #developer documentation #architecture assessment #merge recommendation #maintainer report

Ready to run

npx skills add https://github.com/mighty-hq/mighty-paperclip --skill pr-report-mighty-hq

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It helps maintainers and contributors deeply understand a pull request, translate the change into a tutorial-style explanation, and produce a polished merge-ready report artifact.

Core Features & Use Cases

Deep PR review: Understands the change before judging it, reconstructs the system behavior beyond the diff, and surfaces findings ordered by severity.
Architecture-aware critique: Separates architectural problems from product-scope objections and explicitly distinguishes objection types.
Actionable recommendation + artifacts: Produces a concrete merge recommendation and can generate a structured report (HTML or Markdown) suitable for stakeholders.

Quick Start

Use the pr-report skill to review the pull request in depth and generate a polished HTML or Markdown maintainer 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 review report for a pull request?▼

A deep code review report explains system behavior beyond the diff, separates architectural problems from product-scope objections, and orders findings by severity. It helps maintainers and contributors deeply understand changes and produce a polished merge-ready artifact.

Can I render a standalone HTML report following a specific style guide for my code review?▼

Yes, you can optionally render a standalone HTML report following a bundled style guide and starter template. This produces a structured merge-ready artifact suitable for stakeholders reviewing the pull request changes.

What is the best way to compare design architecture in a large pull request?▼

Applying architecture-aware critique separates architectural problems from product-scope objections and explicitly distinguishes objection types. This approach evaluates structural impact by reconstructing a mental model across layers rather than just inspecting the diff.

Does this code review tool work with branches and worktrees?▼

Yes, the tool applies to scenarios involving PR explanation, deep code review, design comparison, and producing merge decision artifacts for branches or worktrees. It reconstructs system behavior across these contexts to deliver actionable recommendations.

How do I produce an actionable merge recommendation for a complex contribution?▼

The skill produces a concrete merge recommendation by reconstructing a mental model across layers, citing concrete file references, and ordering findings by severity. It translates complex changes into a structured merge-ready artifact for decision making.