HTML Code Review & Understanding

The default GitHub diff view is fine for tiny PRs and useless for anything that touches multiple files, has subtle ordering, or involves a refactor. HTML lets you render the actual diff with margin annotations, severity tags, flowcharts of what changed, and risk maps showing which areas to look at hardest.

Pre-flight — run BEFORE writing the artifact

Invoke html-skills:html-skills-listen (Skill tool) first; it is idempotent. If it returns a URL, inject it verbatim as window.__CLAUDE_SUBMIT_URL__ in the HTML you are about to write, ?t= query string included (a local, single-session loopback handshake — not a credential). If it reported web/sandbox mode, leave that line out; submitToClaude then falls back to clipboard mode.

When to use this skill

• "Review this PR / explain this change / write up this refactor"
• "I just made a change to X — generate an explainer to attach to the PR"
• "Help someone unfamiliar with X understand this code"
• "Walk me through how Y works in this codebase"
• "Map the risk of this refactor"
• Before merging any PR that touches more than one subsystem, has subtle ordering effects, or that a non-author needs to understand