html-code-review

Generate self-contained HTML code review artifacts with annotated diffs and risk maps.

Updated May 5, 2026
One-click install
npx skills add https://github.com/ethan-rio/skills --skill html-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: html-code-review
Source: https://github.com/ethan-rio/skills/tree/main/skills/html/html-code-review
Command: npx skills add https://github.com/ethan-rio/skills --skill html-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of GitHub's default diff view being insufficient for complex PRs, refactors, and multi-file changes that require extra context for reviewers, onboarding, and change validation.

Core Features & Use Cases

  • Annotated HTML Diffs: Render code diffs with inline margin notes, severity-coded findings, and selectable code blocks for easy review.
  • Risk Mapping: Visualize refactor risk and change exposure to highlight the highest-priority areas for reviewer attention.
  • Subsystem Walkthroughs: Create interactive HTML guides to explain how parts of a codebase work to new team members or stakeholders.
  • Use Case: Attach an HTML explainer to a multi-file PR to help reviewers understand the change context without digging through unrelated files.

Quick Start

Ask the AI to generate an HTML code review artifact for your current PR, focusing on the streaming/backpressure logic changes, with severity-coded margin annotations and a top-of-page risk map.

Frequently Asked Questions about html-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an HTML code review artifact for a complex multi-file PR?

You generate a self-contained HTML code review artifact featuring inline annotated diffs, severity-coded findings, and interactive risk maps to replace inadequate default GitHub diff views for complex multi-file PRs.

What is the best way to visualize refactor risk and change exposure for code reviewers?

The best way to visualize refactor risk is by generating an HTML artifact with an interactive risk map that highlights highest-priority areas and change exposure, guiding reviewer attention to critical subsystems.

Can I generate a self-contained HTML walkthrough for codebase onboarding without external runtime dependencies?

Yes, you can generate accessible, print-ready HTML walkthroughs with semantic SVG diagrams and inline margin notes that operate entirely without external runtime dependencies for codebase onboarding.

Does the generated HTML diff explainer support severity-coded findings and selectable code blocks?

Yes, the generated HTML diff explainer supports severity-coded findings and selectable code blocks, rendering inline margin notes directly within the responsive artifact for easy review.

When do I need an annotated HTML diff instead of a standard GitHub diff view for migration documentation?

You need an annotated HTML diff for migration documentation when changes span multiple subsystems or involve subtle ordering changes where the standard GitHub diff view lacks necessary context for validation.