meticulous-review

To review a Meticulous test run, follow the workflow below step by step, using the CLI commands as described.

Before starting, run the meticulous-cli-update skill to ensure the Meticulous CLI is up to date — unless it has already run earlier in this conversation, in which case skip it.

Assess visual frontend changes

Get an overview of the diffs, then visually inspect each one. By default the summary returns a pre-selected representative set — one screenshot per unique structural DOM change — so every returned row is worth inspecting. The rows are returned in priority order (most representative / most significant first), so work through them top to bottom. For each, always look at the screenshot images first (Step 2) — the diff image is the most informative way to understand what actually changed. Use the DOM diff (Step 3) for additional structural detail, and the timeline (Step 4) only when a diff is unexpected and not explained by the DOM or images.

To conclude a PR is good, every returned diff must be checked and confirmed — each one classified as either intended or explained (see the Decision guide). A PR is only safe to approve once there are no unexplained or unintended changes left. The final report should cover all significant visual changes: each deserves its own explanation.

Step 1 -- Get the replay diff summary

Run from the local checkout to resolve the test run from the current commit's git HEAD — the common case when reviewing or babysitting a pull/merge request whose branch is checked out locally. First make sure HEAD matches the remote head CI ran on (e.g. git pull), or you may review a stale or missing run:

meticulous agent test-run-diffs

All non-result output goes to stderr (stdout carries only the diff table); pass --verbose to see the resolved commit and testRunId. To target a run explicitly instead, pass one of: