mirror of https://github.com/cursor/plugins.git synced 2026-09-14 20:00:00 +08:00

Files

T

Alex Vandak Maloney 3b1d0271a9 feat: add pr-review-canvas and docs-canvas plugins

Two first-party Canvas plugins the Cursor Canvas welcome page can
surface via the marketplace query:

- pr-review-canvas: render PR diffs as a Canvas organized by reviewer
  importance — core logic up top, wiring condensed, boilerplate
  summarized, with pseudocode/example traces/callouts for tricky hunks.
- docs-canvas: initial scaffold for rendering documentation
  (architecture, API refs, runbooks, walkthroughs) as a navigable
  Canvas. Skill body is deliberately a starting outline.

Both plugins follow the standard layout (.cursor-plugin/plugin.json +
skills/<name>/SKILL.md + README/CHANGELOG/LICENSE), are registered in
.cursor-plugin/marketplace.json, and added to the root README plugin
table.

Validated locally with `node scripts/validate-plugins.mjs`.

Made-with: Cursor

2026-04-15 11:44:48 -04:00

1.7 KiB

Raw Permalink Blame History

PR Review Canvas

Cursor plugin for rendering pull request diffs as an interactive Cursor Canvas organised for reviewer comprehension rather than file-tree order.

What it includes

pr-review-canvas: build a Canvas that presents a PR diff with core logic up top, wiring/integration condensed in the middle, and boilerplate summarised at the bottom; add pseudocode, example traces, and inline callouts for the parts that are genuinely tricky.

When to use

Reviewing a pull request and you want a walkthrough that surfaces the real risk, not a file-by-file diff.
Summarising a stack of PRs for a human reviewer.
Asking for a diff walkthrough, change-set overview, or "what actually changed here" view.

Trigger it with phrases like "PR review canvas", "review this PR on a canvas", "walk me through this diff on a canvas", or by pointing the agent at a PR URL / branch ref.

How it's organized

The skill groups changes by reviewer value:

Core logic — new behaviour, algorithm changes, state transitions, API surface changes. Full diffs with context.
Wiring & integration — route registration, DI, config plumbing. Condensed.
Boilerplate & mechanical — imports, renames, generated code, formatting. Summarised as a list, no inline diffs unless directly relevant.

It then layers in pseudocode for dense logic, concrete before/after example traces for behaviour changes that are hard to predict from the diff, and inline callouts (Subtle, Breaking, Race condition, Perf) for genuinely surprising or risky hunks.

Requirements

Cursor with Canvas enabled.
Access to the diff source: a local branch/ref (git diff), a GitHub PR URL or number (gh pr diff), or a Graphite stack (gt CLI / gh).

License

MIT

1.7 KiB Raw Permalink Blame History