Create Review Guide

Produce one self-contained HTML file that lets a reviewer understand the implementation top-down — purpose, architecture, where each piece lives, and what changed — before (and while) reading the diff.

1. Resolve the output directory

The output directory is per-installer configuration, resolved in this order:

1. ${CLAUDE_PLUGIN_ROOT}/config.json → outputDir (shared across this plugin's skills)
2. config.json next to this SKILL.md → outputDir (skill-level override)
3. Neither exists → read config.example.json for the expected shape, ask the user for a real absolute path, then write it to the skill-level config.json (git-ignored) so the question is never asked again.

Honor openAfterGenerate (default true) from the same file.

2. Determine the review scope