pr-report

Analyze a pull request and generate a tutorial-style HTML or Markdown review report.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/navyapdh11/navya-cleaning-april --skill pr-report-navyapdh11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-report
Source: https://github.com/navyapdh11/navya-cleaning-april/tree/main/.agents/skills/pr-report
Command: npx skills add https://github.com/navyapdh11/navya-cleaning-april --skill pr-report-navyapdh11

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Reviewers and maintainers often spend substantial time parsing PRs, extracting design rationale, and producing a concise, maintainable report to guide merging decisions. This skill provides a tutorial-style explanation of a PR, turning contributions into a polished artifact that clarifies intent and risks.

Core Features & Use Cases

  • Tutorial-style review: explains the change, architecture, and trade-offs in an accessible format.
  • Maintainer-ready artifact: outputs a standalone HTML or Markdown report suitable for PR documentation and team review.
  • Structured arguments: includes executive summary, tutorial exposition, findings, and a concrete recommendation to support decision-making.
  • Use Case: when evaluating a large feature branch or cross-cutting changes, generate a report that explains design decisions and merge implications.

Quick Start

Analyze the PR branch locally and run the PR Report workflow to generate the 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 report from a pull request?

To generate a maintainer report from a pull request, analyze the PR branch locally and run the PR report workflow to output a standalone HTML or Markdown artifact covering code diffs and architecture decisions.

What is the best way to review large feature branches for merge implications?

Reviewing large feature branches for merge implications is best handled by generating a tutorial-style report that explains design decisions, architecture trade-offs, and recommended actions to guide merging decisions.

Can I output a pull request review as a standalone HTML or Markdown file?

Yes, you can output a pull request review as a standalone HTML or Markdown file. The generated artifact includes structured sections like an executive summary, tutorial exposition, findings, and a concrete recommendation.

Does the PR review report work for small pull requests or only complex changes?

The PR review report works for pull requests of various sizes, complexity levels, and design intents. It parses code diffs and extracts design rationale to produce a concise, maintainable artifact regardless of PR scale.

What should a maintainer-ready pull request review artifact include?

A maintainer-ready pull request review artifact should include an executive summary, a tutorial exposition explaining the change, detailed findings, and a concrete recommendation to support decision-making.

How do I turn code diffs into a tutorial-style explanation for maintainers?

To turn code diffs into a tutorial-style explanation for maintainers, apply the PR report workflow to parse the changes and generate a polished artifact that clarifies intent, architecture, and risks in an accessible format.