pr-report

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

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/Lautaro073/zCorvus_agents --skill pr-report-lautaro073
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-report
Source: https://github.com/Lautaro073/zCorvus_agents/tree/main/AI_Workspace/Agents/Frontend/skills/pr-report
Command: npx skills add https://github.com/Lautaro073/zCorvus_agents --skill pr-report-lautaro073

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The pr-report skill analyzes a pull request to produce a maintainer-grade review that clarifies the changes, rationale, and impact.

Core Features & Use Cases

  • Deep PR analysis from a local branch including diffs, scope, and affected subsystems
  • Tutorial-style explanations of design decisions and tradeoffs
  • Outputs include a standalone HTML report or a Markdown report suitable for docs or chat
  • Uses bundled resources such as references/style-guide.md and assets/html-report-starter.html to present a polished artifact

Quick Start

Run the pr-report skill on a checked-out PR to generate a maintainer-ready 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 a maintainer-ready pull request report?

To generate a pull request report, run the skill on a checked-out local branch to analyze diffs and affected subsystems, producing a polished HTML or Markdown review with architectural context and a merge recommendation.

What should a code review report include for maintainers?

A code review report should include diff analysis, scope evaluation, affected subsystems, tutorial-style explanations of design tradeoffs, and a clear merge recommendation formatted as a standalone HTML or Markdown artifact.

Can I output PR analysis as HTML instead of Markdown?

Yes, PR analysis can be output as a standalone HTML report using bundled starter templates and style guides, or as a Markdown report suitable for documentation and chat platforms.

Does this PR reporting tool require external dependencies?

No, this PR reporting tool requires no external dependencies and leverages local workspace resources, bundled style guides, and starter templates to format maintainer-grade review outputs consistently.

What is the best way to review architectural context in a pull request?

The best way to review architectural context in a pull request is to generate an automated report that analyzes design decisions and tradeoffs, providing tutorial-style explanations and a merge recommendation for maintainers.