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 all diffs, then visually inspect representative screenshots to cover all changes. The domDiffIds from Step 1 tell you which screenshots share the same structural DOM change — pick one representative per unique diff ID to efficiently cover all changes. For each representative, 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. The final report should cover all significant visual changes: each visual change 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 The command prints the resolved testRunId , the commit, and the run status to stderr. To target a run explicitly instead, pass one of: Show more Installs 540 Repository alwaysmeticulous/skills GitHub Stars 2 First Seen May 15, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass