pr-report

Analyze a pull request and generate an HTML or Markdown review report with merge recommendation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Reviewing a PR in large codebases is time-consuming and requires distilling changes, rationale, and trade-offs into a concise, actionable narrative for maintainers.

Core Features & Use Cases

  • Deep PR analysis that explains the changes, design decisions, and potential risks.
  • Polished report artifacts (HTML or Markdown) suitable for sharing with stakeholders.
  • Use Case: when evaluating a large feature, generate a reproducible critique and a recommended merge path.

Quick Start

Provide a deep PR review for a given branch and generate an HTML 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 pull request review report?

To generate a pull request review report, analyze the target branch or PR to distill changes, design rationale, and trade-offs into a structured narrative. This process produces a standalone HTML or Markdown summary artifact suitable for sharing with stakeholders.

What is the best way to explain design decisions and trade-offs in a large contribution?

Explaining design decisions and trade-offs in a large contribution requires deep code analysis to evaluate risks and rationale. You can then compile a reproducible critique with a recommended merge path into a polished Markdown or HTML artifact for governance and review processes.

Can I produce an HTML report for evaluating a large feature branch?

Yes, you can produce an HTML report for a large feature branch. The analysis evaluates the contribution, explains the underlying changes, and generates a standalone HTML artifact with a structured justification and a recommended merge path for stakeholders.

Does the PR analysis include a merge recommendation for maintainers?

Yes, the PR analysis includes a merge recommendation for maintainers. It evaluates the changes and potential risks to provide a structured justification, explaining the rationale behind design decisions to guide the governance and review process.