pr-report

Review pull requests and generate HTML or Markdown reports.

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

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.

Core Features & Use Cases

  • Maintainer-grade review of PRs, branches, or large contributions that explains system design, tradeoffs, and implementation decisions.
  • Generates polished report artifacts (HTML or Markdown) ready for stakeholder sharing or merge-review meetings.
  • Outputs a guided tutorial-style explanation that helps maintainers quickly assess risks, design choices, and recommended actions.

Quick Start

Provide me with a PR patch or link and I will generate a maintainer-grade review 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 pull request review report?▼

A maintainer-grade pull request review report explains system design, tradeoffs, and implementation decisions for large contributions. You provide a PR patch or link to receive a polished HTML or Markdown artifact ready for stakeholder sharing or merge-review meetings.

Can I get an HTML report for a code review and merge decision?▼

Yes, you can generate an HTML report for a code review and merge decision. The process deeply analyzes the PR contribution and outputs a polished HTML or Markdown artifact that explains architectural decisions and offers a clear recommendation.

What is the best way to review large code contributions and explain design tradeoffs?▼

The best way to review large code contributions and explain design tradeoffs is using a structured report that provides a guided tutorial-style explanation. This helps maintainers quickly assess risks, design choices, and recommended actions in a shareable HTML or Markdown format.

Does the PR review report work with Markdown for stakeholder sharing?▼

Yes, the PR review report works with Markdown for stakeholder sharing. It produces polished report artifacts in either HTML or Markdown format, ensuring the maintainer-grade review of system design and tradeoffs is ready for merge-review meetings.

Do I need a PR patch or link to start a design discussion review?▼

Yes, you need a PR patch or link to start a design discussion review. Providing the PR contribution allows the process to deeply analyze the codebase, explain architectural decisions, and generate the final standalone HTML or Markdown report.