pr-review-canvas

Generate interactive HTML PR reviews from GitHub API data.

2.6k|204|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cursor/plugins --skill pr-review-canvas-cursor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-canvas
Source: https://github.com/cursor/plugins/tree/main/cursor-team-kit/skills/pr-review-canvas
Command: npx skills add https://github.com/cursor/plugins --skill pr-review-canvas-cursor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews can be time-consuming and hard to follow when diffs are large or scattered across files. This Skill generates an interactive HTML walkthrough that explains changes clearly and guides reviewers through key areas.

Core Features & Use Cases

  • Fetches PR data from the GitHub API and aggregates title, body, author, and stats.
  • Classifies files into core vs. mechanical changes and renders an annotated diff view.
  • Produces an HTML page with reviewer notes and a collapsible view for easy sharing and archival review.
  • Use case: paste a GitHub PR URL to auto-generate a structured, human-friendly review.

Quick Start

Paste a GitHub PR URL into the tool and render an interactive HTML review.

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 an interactive HTML review from a GitHub PR?

To generate an interactive HTML review, paste a GitHub PR URL into the tool. It fetches PR data via the GitHub API, classifies files, and renders an navigable HTML walkthrough with annotated diffs.

What is the best way to review large GitHub PR diffs without losing context?

The best way to review large diffs is using an interactive HTML walkthrough that classifies core versus mechanical files. This approach aggregates PR stats and guides reviewers through key changes with collapsible views.

Does this PR review tool detect moved code within GitHub diffs?

Yes, the PR review tool detects moved code within GitHub diffs. It fetches diff data via the GitHub API and marks relocated code blocks directly in the rendered interactive HTML output.

Can I add reviewer annotations to an automated PR diff analysis?

Yes, you can add reviewer annotations to the automated diff analysis. The generated HTML page includes reviewer notes alongside the classified core and mechanical file changes for easy archival.

Do I need the GitHub API to classify core versus mechanical PR files?

Yes, you need the GitHub API to fetch the data required to classify core versus mechanical PR files. The tool makes API calls to retrieve PR diffs, comments, and metadata for rendering the HTML output.

Why use an interactive HTML page for GitHub PR reviews instead of standard diffs?

An interactive HTML page provides a structured, human-friendly review by classifying files and adding collapsible views. Standard GitHub diffs scatter changes, making large PRs hard to follow and archive.