pr-report

Analyze GitHub pull requests and generate HTML or Markdown reports with merge recommendations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Joaoha/xenon-maas --skill pr-report-joaoha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-report
Source: https://github.com/Joaoha/xenon-maas/tree/main/.agents/skills/pr-report
Command: npx skills add https://github.com/Joaoha/xenon-maas --skill pr-report-joaoha

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Review pull requests and contributions deeply, explain design decisions tutorial-style for maintainers, and produce a polished report artifact such as HTML or Markdown.

Core Features & Use Cases

  • In-depth PR analysis with explanation of architecture and rationale
  • Generate standalone HTML or Markdown reports suitable for code reviews and audits
  • Compare designs to similar systems and provide actionable merge recommendations

Quick Start

Provide a maintainer-grade review of a PR and generate a polished HTML or Markdown 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 an automated PR review report for maintainers?▼

Generate a maintainer-grade PR review report by analyzing pull requests deeply to explain system design and decision-making. The output is a polished HTML or Markdown report stored in an accessible directory like tmp/reports.

What is the best way to analyze a pull request for architectural decisions before merging?▼

Analyzing a pull request for architectural decisions involves evaluating the system design and rationale tutorial-style. This approach compares designs to similar systems and provides actionable merge recommendations for maintainers.

Can I produce HTML or Markdown reports for GitHub branches and large contributions?▼

Yes, you can apply deep PR analysis to GitHub PRs, branches, and large contributions. The process produces standalone HTML or Markdown report artifacts suitable for code reviews and audits.

How do I explain code design decisions tutorial-style in a pull request review?▼

Explain code design decisions by analyzing the contribution deeply and generating a report that outlines the architecture and rationale. The output serves as a tutorial-style explanation for maintainers.

Does a maintainer-grade pull request report include a merge recommendation?▼

Yes, a maintainer-grade pull request report includes a merge recommendation. It also provides an architectural explanation and compares the submitted design to similar systems to guide the final decision.