pr-report

Generate maintainer-grade PR review reports from a target branch or diff.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kysonttan-sys/1percent-AI-Labs --skill pr-report-kysonttan-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-report
Source: https://github.com/kysonttan-sys/1percent-AI-Labs/tree/main/.agents/skills/pr-report
Command: npx skills add https://github.com/kysonttan-sys/1percent-AI-Labs --skill pr-report-kysonttan-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of a maintainer-grade PR review artifact, translating complex changes into a clear, structured report that guides decision-makers.

Core Features & Use Cases

  • Deep PR analysis: explains design decisions, architecture changes, and risk factors.
  • Artifact generation: outputs standalone HTML or Markdown reports suitable for merge reviews.
  • Tutorial-style guidance: helps maintainers understand the rationale behind changes and recommended next steps.

Quick Start

Load the target PR (or branch) and generate a polished 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 PR review report from a branch diff?

Generate a maintainer-grade PR review report by loading a target branch or diff to analyze design decisions and architectural risks, producing a standalone HTML or Markdown artifact with an executive summary and merge recommendation.

What is included in an automated pull request architecture analysis?

An automated pull request architecture analysis includes a structured executive summary, tutorial-style explanation of design decisions, identified risk factors, and a concrete merge recommendation formatted as a self-contained HTML or Markdown report.

Can I output my code review findings as a standalone HTML or Markdown file?

You can output code review findings as a standalone HTML or Markdown file, containing structured executive summaries, tutorial-style explanations of architectural changes, and actionable merge recommendations suitable for distribution.

Does this automated PR review tool work for large codebase contributions?

This automated PR review tool works for large codebase contributions, applying architectural reasoning and design decision analysis across branches or major pull requests to generate structured merge recommendations.

What is the best way to document architectural changes for code maintainers?

The best way to document architectural changes for maintainers is generating a tutorial-style report that translates complex diffs into a structured executive summary with actionable next steps and clear merge recommendations.

When do I need a structured PR review report instead of inline code comments?

You need a structured PR review report instead of inline comments when translating complex changes across large contributions, requiring an executive summary, architectural reasoning, and a formal merge recommendation for decision-makers.