review-reportlisted
Install: claude install-skill Hiveteq/review-report
# Review Report
Turn a diff into an HTML walkthrough for a colleague who knows the codebase before this change but has not
seen the change. Explain what is new, why, and how it touches existing code; explain existing code only where
the change hinges on it. You write a story JSON; `render.mjs` does the HTML. Never hand-write HTML or copy
diff text. `$SKILL` is `${CLAUDE_SKILL_DIR}`; contract, conventions and errors are in
`$SKILL/reference/story-schema.md`.
## Workflow
1. **Dump:** `node $SKILL/render.mjs --dump-numbered [--target <spec>]`. Anchors come from its `old`/`new`
columns, never from counting or Read-tool line numbers. Targets: none (vs master/main), `#123`, `A..B`,
`<commit>`, `--staged`, `--working`.
2. **Read surrounding code** where the diff does not explain intent.
3. **Write the story** to the scratchpad.
4. **Render:** `node $SKILL/render.mjs --story <path> [--target <spec>]`, fix every `error:` line and resolve every
anchor `warning:` (a note naming code that sits on a neighbouring line). It
refuses under 80% of changed lines shown or a chapter over 1,000 lines. Never lower `--min-coverage`;
add chapters or `exclude` with a reason.
5. **Reader pass, two rounds:** a fresh subagent gets the report, read-only base-commit code and the brief in
`$SKILL/reference/reader-pass.md`, and lists where it had to guess. Answer each question with a note,
re-render, run one more fresh reader. Its leftovers go to `meta.readerPass.openQuestions` and to