Compare two recorded browser sessions at matching step IDs using screenshots and accessibility snapshots, which describe page elements. Report the first difference and overall similarity to check interface changes or verify replayed sessions.
Visual + DOM diff between two recorded sessions at matching trajectory step ids; used for visual regression and replay verification
Review the instructions the agent will receive before you install.
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.27 rvf status <session-id-a>.rvf
npx -y ruvector@0.2.27 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.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.