skills.rest
windingriverholdings
windingriverholdingsOFFICIAL
Explore all skills by this author →
GitHub

pr-report

Analyze pull requests and generate HTML or Markdown review reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

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. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.

Core Features & Use Cases

  • Produce a maintainer-grade review of a PR, branch, or large contribution.
  • Output a polished report artifact (HTML or Markdown) suitable for publication or review.
  • Workflow guidance and standardized structure to compare designs and justify decisions, including an executive summary and recommendations.

Quick Start

Run a full maintainer report on the given PR by loading local changes, comparing against docs, and exporting a ready-to-publish HTML or Markdown artifact.

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-ready pull request review report?▼

Generate a maintainer-ready pull request review report by loading local changes, comparing them against existing documentation, and exporting a ready-to-publish HTML or Markdown artifact with an executive summary.

What is the best way to explain a contributor's design decisions for code review?▼

Explaining a contributor's design decisions involves identifying the core problem addressed by the pull request, articulating its impact on the codebase, and describing the subsystems it touches for tutorial-style maintainer review.

Can I export code review analysis as both HTML and Markdown?▼

Yes, you can export code review analysis as both HTML and Markdown. The review process produces a polished report artifact suitable for publication that satisfies specific format requirements and tooling expectations.

What should be included in a pull request report for maintainers?▼

A pull request report for maintainers should include the PR's scope, typical review use cases, an executive summary, design comparisons, and a merge recommendation to justify decisions.

Does this pull request analysis workflow require external dependencies?▼

No, this pull request analysis workflow requires no external dependencies. It operates independently to load local changes, compare designs, and produce standardized maintainer-grade review artifacts.

When do I need to produce an executive summary for a code review?▼

You need to produce an executive summary for a code review when preparing a maintainer-grade report on a large contribution, ensuring the standardized structure clearly compares designs and justifies merge recommendations.

Related Skills

Explore More Software Engineering Skills→
Kord96Kord96

publish

Push the current git branch to origin with optional draft PR and Codex review.

Community
Intermediate
travelinman1013travelinman1013

pr-report

Analyze pull requests and generate HTML or Markdown review reports.

Community
Advanced
nanorepublicananorepublica
61

Global Tech Stack

Validate code against centralized global tech stack standards.

Community
Basic
Lautaro073Lautaro073

pr-report

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

Community
Advanced