pr-report

Ask for a deep review of the target branch or PR and the skill works from local code rather than just the GitHub page. It reconstructs the system design, lists findings by severity with file references, and ends with a concrete merge recommendation.

Request a webpage or HTML report for the PR and the skill builds a standalone HTML artifact, typically starting from the bundled html-report-starter.html template. It follows the bundled style guide for typography, layout, and color so the report reads like an editorial review.

The skill produces standalone HTML reports in a tmp/reports folder, Markdown reports in a report folder or another requested location, and a short maintainer summary directly in chat. The chat summary stays shorter than the full report.

Yes, when a contribution introduces a framework or platform concept, the review compares it to similar open-source systems using official docs or source. Comparisons focus on extension boundaries, context passing, trust models, and UI ownership.

Findings are ordered by severity, prioritizing behavioral regressions, trust or security gaps, misleading abstractions, lifecycle and operational risks, hard-to-unwind coupling, and missing tests. Each finding cites concrete file references where possible.

The full workflow is designed for large or architecturally significant contributions where a maintainer-grade judgment is needed. For small typo fixes or trivial diffs, a lightweight inline review is more appropriate than building a structured report artifact.