pr-report

Generate maintainer-grade pull request reviews with HTML or Markdown reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides in-depth analysis and maintainer-grade reviews for pull requests, branches, or significant code contributions, transforming complex changes into clear, actionable reports.

Core Features & Use Cases

  • Deep Code Review: Analyzes code changes, design decisions, and architectural implications.
  • Tutorial-Style Explanations: Explains the system and the contribution as if teaching from first principles.
  • Artifact Generation: Produces polished reports in formats like HTML or Markdown.
  • Use Case: A maintainer can use this Skill to get a comprehensive review of a complex feature PR, including a clear recommendation on whether to merge, what needs redesign, and a comparison to similar open-source systems.

Quick Start

Use the pr-report skill to generate a detailed HTML report for the current PR.

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 comprehensive code review report for a pull request?

To generate a pull request code review report, this Skill analyzes code changes, design decisions, and architectural implications, then outputs a polished maintainer-grade review artifact in HTML or Markdown.

Can I get an architectural analysis and merge recommendation for a complex branch?

Yes, you can get an architectural analysis and merge recommendation for a complex branch. The Skill evaluates system architecture, lifecycle, and trust boundaries to provide actionable merge or redesign guidance.

How do I explain contributor design decisions and system comparisons in my documentation?

To explain contributor design decisions, this Skill generates tutorial-style explanations from first principles and compares the contribution against similar open-source systems within its code analysis reports.

Does this code analysis tool work without external dependencies?

Yes, this code analysis tool works without external dependencies. The Skill operates independently using its internal components to generate comprehensive reporting artifacts for code contributions.

What is the best way to document deep code contributions for maintainers?

The best way to document deep code contributions is using this Skill to transform complex changes into clear, actionable HTML or Markdown reports that address PR analysis and system architecture.

When do I need an advanced PR analysis report instead of a standard code review?

You need an advanced PR analysis report when evaluating significant code contributions that require deep understanding of system architecture, lifecycle, and trust boundaries to produce actionable maintainer-grade recommendations.