pr-review-canvas SKILL.md skillC
pr-review-canvas from cursor/plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cursor/plugins/pr-review-canvas@git:20260301.469d9f7Pins git:20260301.469d9f7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- C, 15 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cursor/plugins
- Path
cursor-team-kit/skills/pr-review-canvas/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260301.469d9f7, committed Mar 1, 2026
- Size
- 9,088 bytes
- Repository stars
- 15,586
- License
- none declared
Generate an interactive PR review walkthrough as an HTML page. Fetches PR data via gh API, categorizes files into core vs mechanical changes, adds reviewer annotations, and renders diffs with moved-code detection. Use when the user pastes a GitHub PR URL and asks for a review, walkthrough, or summary, or says "review this PR".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# PR Review Canvas
Generate an interactive HTML review of a GitHub PR that reads like a peer walking you through what matters.
## Workflow
### 1. Fetch PR data
Run these `gh api` calls in parallel:
```bash
gh api repos/{owner}/{repo}/pulls/{number} --jq '{title, body, user: .user.login, state, additions, deletions, changed_files, base: .base.ref, head: .head.ref}'
gh api repos/{owner}/{repo}/pulls/{number}/files --paginate --jq '.[] | {filename, status, additions, deletions, patch}'
gh api repos/{owner}/{repo}/pulls/{number}/comments --jq '.[] | {user: .user.login, body, path, line}'
```
### 2. Analyze the PR and write the body HTML
Read the diffs, understand the PR, and write the `<body>` content directly as HTML. You have full creative freedom -- the goal is to explain the PR clearly to a reviewer. Use whatever structure best fits the PR.
**Typical structure** (adapt as needed):
- Header with title, PR number, author, stats
- Summary box explaining what the PR does in plain English
- Core file sections with annotations and diffs
- Mechanical/boilerplate files collapsed by default
- Review checklist at the bottom
**But you can also add:**
…Read the whole file at its exact version.
How to install
mdr add cursor/plugins/pr-review-canvas@sha256:88a07a2459197acbThe line at the top of this page pins the label git:20260301.469d9f7, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qso2ah4zb4lzusio)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 1, 2026.
Audit of the latest version
- fail: No link to a raw IP address (matched: http://127.0.0.1:8432)
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9088 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
cursor/plugins · 15,586 stars · license none declared · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qso2ah4zb4lzusio GET https://markdownregistry.com/api/v1/resolve?ref=cursor/plugins/pr-review-canvas GET https://markdownregistry.com/api/v1/blob/88a07a2459197acba3c5e06b7d695e35ad618a998442b72d05cdba4efc117ac6
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.