human-review

Assemble a tabbed HTML review page for a change set from committed review records and measured evidence.

6|7|Updated Aug 21, 2026
One-click install
npx skills add https://github.com/victorrentea/human-review --skill human-review-victorrentea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: human-review
Source: https://github.com/victorrentea/human-review/tree/main/skills/human-review
Command: npx skills add https://github.com/victorrentea/human-review --skill human-review-victorrentea

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Pillow, pygments, and includes scripts (resource) and references (resource) components.

What problem does it solve? Human code review of an agent-written branch is slow and error-prone: the reviewer must reconstruct what was changed, what was already reviewed, what the diagrams and REST contract did, and which tests pin the behavior. This Skill assembles all of that into one self-contained, tabbed review.html page whose snippets are cut from the working tree at build time, so the page cannot drift from the code it describes. ## Core Features & Use Cases - Review record rendering: Reads the review-points.md file the coding agent committed with its fixes (what it fixed, declined, and assumed) and renders the three piles verbatim, never inventing findings of its own. - Deterministic evidence producers: One command runs diagram deltas, sequence diagrams, a C4 container view, a Code City snapshot, a narrated feature video, endpoint-complexity deltas, REST contract diffs, logging and design-system audits, code owners, and Playwright traces, each gated on its own prerequisites. - Deep-linked, incremental page: Every code reference clicks into the editor, snippets are extracted at build time, and refreshes re-run only the producers whose inputs moved. - Use Case: After running /implement-ticket on a branch, invoke /human-review origin/main to get a single page a human reviewer can open in the browser to approve a pull request in minutes. ## Quick Start Run /human-review origin/main in the repository to build and serve the tabbed review page for this branch against its base.

Frequently Asked Questions about human-review

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

FAQPage Schema
How do I generate a human review page for a pull request?

Run /human-review with a PR number or URL, such as /human-review 123. The skill checks out the PR, resolves the base ref, runs the evidence producers, and serves a tabbed review.html page with the review record, diagrams, video, and tests.

What is review-points.md and why does the skill need it?

review-points.md is the record the coding agent commits with its fixes, listing what it fixed, declined, and assumed during its own review. The skill reads it verbatim and never runs a new review, so the page shows decisions made by the agent that wrote the code.

Does human-review work without a review-points.md file?

Yes, the page still builds and renders a band stating that nothing records what was reviewed or declined. The skill explicitly refuses to fabricate the piles, and suggests running /implement-ticket on a fresh implementation to produce the record.

How do I configure project-specific commands for the evidence steps?

Copy human-review.example.json to human-review.json at your repository root and fill in the steps your project supports, such as video.app, dsaudit screens, and city test commands. Any step not configured is skipped and named under the tab strip.

Why does the feature video step get skipped or film the wrong branch?

Without a video.app block the recorder only checks that something answers on the default ports, which can be another checkout of the same repository. Configuring app up/url/down commands makes the run build and film the exact commit under review.

Can I refresh the review page without re-running everything?

Yes, refresh-report.py re-runs only producers whose inputs changed, keyed on git pathspecs rather than timestamps. Use --steps static, cheap, or all to control scope, and --force to ignore the cache entirely.