visual-recaplisted

Side-route skill that renders a change as a single self-contained interactive HTML artifact — a finished diff, PR, or branch, or a plan's decisions and architecture before any of it is built. Three block sets: a scrolling recap for auditing a change (file-tree + change flags, annotated split diffs with line-anchored callouts, schema/API contract cards, UI wireframes, before/after columns, a per-unit series when one root cause repeats across four or more near-identical sites), a paged walkthrough deck for arguing a reader through one (premise → changes → mechanism → aftermath), and forward-looking blocks for a plan (decision cards, options comparisons, architecture diagrams — every field cited or visibly asserted). Diagrams take a CSS spine when trivial and Mermaid-via-CDN when multi-stage or behavioral. Use when a reader who didn't author the change or the plan needs to grasp its shape before reading prose. Optional and never auto-invoked; skip small or obvious diffs, and plans whose decisions foreclose nothi
chrislacey89/skills · ★ 3 · API & Backend · score 72

Install: claude install-skill chrislacey89/skills

# Visual Recap Render a finished change as a single self-contained interactive HTML file that shows a reviewer the *shape* of the diff before they read the lines: which surfaces moved, which hunks are load-bearing, what's risky — with callouts anchored to the exact lines, then a drop into the literal code. The output is **reviewer comprehension as a portable artifact**, not a defect list. It renders in one of **two modes**, chosen in Step 1 and never defaulted into: a **scrolling recap** when the reviewer is auditing a change, and a **walkthrough deck** — one idea per screen, premise → changes → mechanism → aftermath — when the reviewer has to be argued through one. This skill exists because Cohen's strongest empirical finding is *author preparation*: an annotated walkthrough prepared by someone who understands the change correlates with near-zero defect variance. The pipeline produces that annotation as terminal prose (`/pre-merge`, `/walk-commits`) but never as a highlightable, shape-first surface — so the reviewer rebuilds the change's topology in their own head before judging any line. `/visual-recap` produces the missing surface (Meadows: a missing high-bandwidth feedback flow in the review loop) **without any lock-in** — the agent authors the HTML directly; there is no renderer package, no build system, no server, no MCP connector, and no hosted database. GitHub PR review comments stay the durable channel. It also renders the *forward* direction — a plan's decisions