create-review-guidelisted
Install: claude install-skill atman-33/workhub
# 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](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
Pick the first that applies; confirm with the user only if ambiguous:
- The user named a branch, PR, or commit range → use exactly that
(`git diff <base>...<head>`).
- The working tree is dirty → uncommitted changes (`git diff HEAD`, plus
`git diff --staged` if partially staged).
- On a feature branch → `git diff $(git merge-base main HEAD)...HEAD` and
`git log` for that range. (Fall back to `master`/`develop` if `main` is absent.)
- On the default branch with a clean tree → ask the user what to review.
## 3. Gather real content — never fabricate
- Run `git log --oneline` for the range and `git diff --stat` for the shape of the change.
- Read