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.

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

Output requirements

Render diffs as real HTML so reviewers can copy lines. Use a monospace font for code and a readable serif or sans for prose. Reviewers will open this on a phone during a commute, so the responsive collapse from the foundation block is load-bearing here.

Include a header with: PR title, author, branch, and a one-sentence summary. End with a "what to look at hardest" section that ranks the diff by reviewer attention required.