skills.rest
santhank8
santhank8COMMUNITY
Explore all skills by this author →
GitHub

pr-report

Analyze pull requests and generate standalone HTML or Markdown reports.

Updated Apr 13, 2026
Search Tags:#analysis#code-review#pr-review#markdown-report#html-report#maintainer-report
One-click install
npx skills add https://github.com/santhank8/paperclone --skill pr-report-santhank8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-report
Source: https://github.com/santhank8/paperclone/tree/main/.agents/skills/pr-report
Command: npx skills add https://github.com/santhank8/paperclone --skill pr-report-santhank8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown.

Core Features & Use Cases

  • Deep PR analysis that explains the system built, not just the diff, with architectural and product implications.
  • Tutorial-style explanations for maintainers to understand contributor intent and design decisions.
  • Generate standalone HTML or Markdown reports suitable for code reviews, documentation updates, or merge recommendations.
  • Compare the PR to similar designs or patterns and surface tradeoffs, risks, and improvement opportunities.
  • Provide actionable recommendations and a clear artifact ready for sharing with stakeholders.

Quick Start

Provide a PR and any context to the agent and request a maintainer-grade report in HTML or Markdown.

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 report in Markdown or HTML?▼

To generate a maintainer-grade PR review, provide the pull request and context to the agent to produce a standalone Markdown or HTML report explaining the system architecture and merge recommendations.

What is a deep pull request analysis and how does it differ from a standard code review?▼

A deep pull request analysis explains the system built rather than just the diff, providing tutorial-style explanations of contributor intent, architectural implications, and design decisions for maintainers.

Can I use this approach to review design explanations and merge recommendations across different codebases?▼

Yes, you can apply this analysis to pull requests, design explanations, and merge recommendations across codebases to surface tradeoffs, risks, and improvement opportunities with concrete file references.

What is the best way to compare a pull request to similar design patterns and surface tradeoffs?▼

The best way to compare a pull request to similar designs is to analyze the contribution deeply, which surfaces architectural tradeoffs, risks, and improvement opportunities in a polished report artifact.

How do I create a standalone code review artifact suitable for sharing with stakeholders?▼

You can create a standalone code review artifact by analyzing the pull request deeply and generating a polished HTML or Markdown report that includes actionable recommendations and design explanations.

Related Skills

Explore More Software Engineering Skills→
tkstangtkstang

create-pr-description

Generate pull request descriptions from git diffs and Jira tickets.

Community
Intermediate
wwa-labwwa-lab

legacy-html-exporter

Convert Markdown files to standalone HTML companion documents.

Official
Basic
AsiaOstrichAsiaOstrich
70

discover

Assess project health, architecture, and risks in existing codebases.

Community
Intermediate
lvndrylvndry
47

pr-description

Generate PR titles and descriptions from diffs and branch context.

Community
Intermediate