pr-report

Analyze pull requests and generate HTML or Markdown technical reports.

Updated May 27, 2026
One-click install
npx skills add https://github.com/bychrisr/now-company --skill pr-report-bychrisr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-report
Source: https://github.com/bychrisr/now-company/tree/main/.agents/skills/pr-report
Command: npx skills add https://github.com/bychrisr/now-company --skill pr-report-bychrisr

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the challenge of performing deep, architectural code reviews by automating the synthesis of complex changes into clear, maintainable, and actionable reports.

Core Features & Use Cases

  • Maintainer-Grade Analysis: Produces structured reviews that evaluate architectural integrity, security, and design decisions rather than just surface-level diffs.
  • Artifact Generation: Creates polished, standalone HTML or Markdown reports suitable for sharing with stakeholders or documenting design rationale.
  • Use Case: When a large, complex contribution is submitted, use this skill to generate a tutorial-style report that explains the system design, highlights potential risks, and provides a concrete merge recommendation.

Quick Start

Use the pr-report skill to analyze the current pull request and generate a comprehensive HTML report in the tmp/reports directory.

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?

To generate a maintainer-grade pull request review, analyze the code contribution to reconstruct system design models, evaluate architectural risks, and compare implementations against industry precedents to produce actionable merge recommendations.

What is architectural code review and when do I need it for a large contribution?

Architectural code review evaluates design integrity, security, and architectural risks rather than surface-level diffs. You need it when a large, complex contribution is submitted and requires deep analysis to synthesize changes into clear, maintainable reports.

Can I share pull request analysis reports with stakeholders as standalone documents?

Yes, you can share pull request analysis reports with stakeholders. The process generates polished, standalone HTML or Markdown reports in the tmp/reports directory that are suitable for documenting design rationale and explaining system design.

Do I need local codebase access to analyze complex pull requests?

Yes, local codebase access is required to analyze complex pull requests. The analysis requires access to local codebases and documentation to reconstruct system design models and generate tutorial-style summaries with concrete merge recommendations.

What's the best way to document design rationale for complex code contributions?

The best way to document design rationale is to generate a tutorial-style report that reconstructs the system design model, highlights potential architectural risks, and provides a concrete merge recommendation based on industry precedents.

Are there limitations to automated code review for architectural risks?

Automated code review for architectural risks is limited by its reliance on local codebase and documentation access. It focuses on architectural integrity and design decisions rather than surface-level diffs, making it less suited for quick, superficial syntax checks.