pr-review-canvas

Generate interactive HTML PR review walkthroughs from GitHub pull request data.

Updated May 18, 2025
One-click install
npx skills add https://github.com/nthpaul/dotfiles --skill pr-review-canvas-nthpaul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-canvas
Source: https://github.com/nthpaul/dotfiles/tree/main/cursor/.cursor/plugins/cache/cursor-public/cursor-team-kit/d1cdb88a9eb33cf392395c87e3fd76419fc1010e/skills/pr-review-canvas
Command: npx skills add https://github.com/nthpaul/dotfiles --skill pr-review-canvas-nthpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing a GitHub pull request is slow and easy to misprioritize, especially when changes span core logic and mechanical churn.

Core Features & Use Cases

  • Generates an interactive PR review HTML walkthrough that explains the change as if a peer were guiding you through it.
  • Fetches PR metadata and diff context via the GitHub CLI (gh API), including PR details, changed files, file patches, and existing review comments.
  • Organizes files into core vs mechanical changes so you can focus on what matters first, with core files expanded by default.
  • Renders unified diffs with moved-code detection to highlight likely refactors vs true logic changes.
  • Adds reviewer-friendly annotations and a review checklist to make the output actionable in a real code review workflow.

Quick Start

Use the pr-review-canvas skill when you paste a GitHub PR URL and ask for a review walkthrough or summary.

Frequently Asked Questions about pr-review-canvas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a walkthrough review from a GitHub pull request?

Generate a PR review walkthrough by fetching pull request metadata and file diffs via the GitHub CLI, then rendering them into an interactive HTML summary. The output organizes files into core logic and mechanical churn to prioritize your review.

How does moved code detection work in a diff rendering?

Moved code detection in diff rendering highlights likely refactors versus true logic changes within a GitHub pull request. By fetching file patches via the gh API, the HTML renderer visually distinguishes relocated code from newly added or modified logic.

Do I need the GitHub CLI installed to review a PR link?

Yes, you need the GitHub CLI installed and authenticated to review a PR link. The tool fetches pull request details, changed files, file patches, and existing review comments directly through the gh API as its core data source.

What is the best way to summarize a GitHub pull request with many mechanical changes?

The best way to summarize a GitHub pull request with mechanical changes is to use a tool that organizes files into core logic versus churn. This HTML walkthrough expands core files by default, helping you focus on what matters first.

Can I get an HTML summary of existing GitHub review comments for a pull request?

Yes, you can get an HTML summary of existing GitHub review comments for a pull request. The tool fetches existing review comments via the gh API and integrates them into an interactive walkthrough with reviewer-friendly annotations.