Agent skill · writing content · cursor
pr-review-canvas
Render a PR diff review as a Cursor Canvas that groups changes by reviewer importance, separates boilerplate from core logic, and highlights tricky or unexpected code. Use when reviewing a pull request, summarizing a diff for review, or when the user asks for a PR review canvas, diff walkthrough, or change-set overview.
Why this skill is useful
Provides a structured approach to PR reviews that enhances comprehension and highlights critical changes, which the AI wouldn't generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-06. 2,555 stars on the source repository.
What this skill does
PR Review Canvas Build a canvas that presents a PR diff reorganized for reviewer comprehension — not in file-tree order. Prerequisites Read ~/.cursor/skills-cursor/canvas/SKILL.md first. It contains the generation policy, design guidance, slop rules, self-check, and file-path conventions you must follow. The full component and hook surface is declared in ~/.cursor/skills-cursor/canvas/sdk/index.d.ts and its sibling .d.ts files — read them to discover exact exports and prop shapes rather than guessing. Gather the diff Expect a GitHub PR link (a full URL like https://github.com/<owner>/<repo>/pull/<n>, or an equivalent gh-resolvable reference). Use gh pr diff <pr> to collect every file's path, additions, deletions, and hunks. If the user didn't provide a PR link, stop and ask. Do not guess at the current branch, infer from recent history, or fall back to a local git diff. Ask the user which diff they want to review — a specific PR URL or number — and wait for their reply before continuing. Group changes for comprehension Do not present files in alphabetical or tree order. Reorganize into sections ordered by reviewer value: 1. Core logic — New behavior, algorithm changes, state transitions, API surface changes. Show full diffs with surrounding context. 2. Wiring & integration — Route registration, dependency injection, config plumbing that connects the core logic. Condensed — enough to confirm correctness. 3. Boilerplate & mechanical — Import reordering, renames, generated code, formatting, type re-exports. Summarize as a list of file names and stats. No inline diffs unless specifically relevant. Lead with core logic. The reviewer's attention is freshest at the top. Distill complex logic into pseudocode When a core change involves dense or intricate logic — deeply nested conditions, state machines, retry/backoff flows, multi-step transformations — add a short pseudocode summary next to the diff. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills cursor/pr-review-canvas--5868b7