Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From pr-review-canvas
Render a PR diff review as an interactive walkthrough 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, or asking for a diff walkthrough.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pr-review-canvas:pr-review-canvasThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build an interactive review walkthrough that presents a PR diff reorganized for reviewer comprehension — not in file-tree order.
Build an interactive review walkthrough that presents a PR diff reorganized for reviewer comprehension — not in file-tree order.
Expect a GitHub PR link (full URL or 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.
Reorganize into sections ordered by reviewer value:
When a change involves dense logic, add a short pseudocode summary next to the diff.
Pick a concrete input and walk it through both old and new code paths side-by-side for genuinely surprising behavior changes.
Tag surprising/risky hunks with labels like "Subtle", "Breaking", "Race condition", "Perf" and a one-sentence explanation.
Generate an HTML page with categorized sections, diff views, and annotated findings.
npx claudepluginhub andersonlimahw/lemon-ai-hub --plugin pr-review-canvasRender 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.
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".
Render a GitHub Pull Request diff as a self-contained HTML page where each changed hunk is annotated with a software-principle explanation and a suggested simplification. Use when the user wants to review a PR visually, generate an HTML/visual diff report, or see PR feedback linked to principles (e.g. an unnecessary useMemo/useCallback) before commenting. Don't use for text-only PR feedback (use code-review), browser UI screenshots (use visual-validate), or orchestrating multiple reviewers (use review).