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.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
npx claudepluginhub andersonlimahw/lemon-ai-hub --plugin pr-review-canvas