with one click
browser-screenshot-diff
Visual + DOM diff between two recorded sessions at matching trajectory step ids; used for visual regression and replay verification
Menu
Visual + DOM diff between two recorded sessions at matching trajectory step ids; used for visual regression and replay verification
| name | browser-screenshot-diff |
| description | Visual + DOM diff between two recorded sessions at matching trajectory step ids; used for visual regression and replay verification |
| argument-hint | <session-id-a> <session-id-b> [--threshold <0..1>] [--mode pixel|dom|both] |
| allowed-tools | mcp__claude-flow__browser_eval Bash Read Write |
Compare two recorded sessions step-by-step. Pairs each step in session A to the same step-id in session B, diffs the captured screenshot and accessibility snapshot, reports the first divergence and an aggregate similarity score.
browser-replay run matches the parent session within tolerance.npx -y ruvector@0.2.25 rvf status <session-id-a>.rvf
npx -y ruvector@0.2.25 rvf status <session-id-b>.rvf
trajectory.ndjson. Build a step-id → (screenshot_path, snapshot_path) map for each.step-id. Steps that exist on only one side are flagged as unmatched and contribute to the divergence score.--mode pixel|both): compare the two PNGs at each step. Report mse, psnr, and the bounding box of the largest diff cluster. Threshold default 0.02 (2% of pixels).--mode dom|both): compare the accessibility snapshots node-by-node. Report added / removed / changed nodes with their accessible names.findings.md under a fresh RVF container so the diff itself is replayable.browser-sessions under both source ids' tags so future searches surface "ran a diff against session X".browser_screenshot_diff MCP tool is not planned (ADR-0001 §7); the skill operates against locally-saved RVF artifacts and uses browser_eval only for live verification.Spawn nested sub-agents (agents that spawn sub-agents, up to depth=5) via Claude Code's native Task tool — for context-managed deep delegation
Author a workflow — either an MCP workflow template (persisted, lifecycle) or a native .claude/workflows/*.js orchestration script (agent/parallel/pipeline fan-out)
Run a workflow — drive an MCP workflow lifecycle (execute/pause/resume/cancel) or invoke + resume a native .claude/workflows/*.js orchestration via the Workflow tool
Side-by-side comparison of ruflo vs HAL vs other GAIA harnesses — capability gaps, design decisions, and improvement roadmap
Diagnose why a GAIA question failed — extract trace, classify failure mode, and propose a fix
Walk through a complete GAIA benchmark→submit flow — from key resolution through HAL-compatible package generation