pr-report

Analyze pull requests and generate maintainer-focused HTML or Markdown reports.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/a7garden/CoHalo --skill pr-report-a7garden
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-report
Source: https://github.com/a7garden/CoHalo/tree/main/skills/pr-report
Command: npx skills add https://github.com/a7garden/CoHalo --skill pr-report-a7garden

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. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.

Core Features & Use Cases

  • Deep PR analysis and explanation that prioritizes architectural clarity over diffs
  • Tutorial-style guides that educate maintainers about design decisions and tradeoffs
  • Output-ready artifacts (HTML or Markdown reports) suitable for sharing with stakeholders

Quick Start

Provide a detailed PR review and generate a ready-to-share report for a given pull request.

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 in markdown or HTML?

Generate a PR review report by analyzing the pull request changes, architectural intent, and risks, then outputting a polished markdown or HTML artifact with actionable recommendations for maintainers.

What is the best way to explain a contributor's design decisions in a pull request?

Explain a contributor's design decisions by applying a deep PR analysis that prioritizes architectural clarity over simple diffs, generating a tutorial-style guide focused on tradeoffs and structural implications.

Does this PR review process identify potential risks before merging a patch?

Yes, the PR review process identifies potential risks by evaluating the patch against a target branch, summarizing architectural implications and contributor decisions to prepare a clear merge recommendation.

How do I prepare an actionable merge recommendation for a complex pull request?

Prepare a merge recommendation by summarizing the PR's changes and intent, then generating a maintainer-focused explanation that highlights architectural risks and actionable next steps.

Can I compare a contributor's design decisions with similar systems during a code review?

Yes, you can compare a contributor's design decisions with similar systems during a code review to educate maintainers about tradeoffs and generate a shareable report artifact.

Are there limitations to using automated PR review reports for stakeholder sharing?

Automated PR review reports focus on architectural implications rather than line-by-line code correctness, meaning they complement but do not replace detailed manual code reviews for stakeholders.