browser-review

Collects element-level browser annotations on HTML artifacts and gates completion on layout audits.

20|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reddb-io/red-skills --skill browser-review-reddb-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-review
Source: https://github.com/reddb-io/red-skills/tree/main/plugins/dev/skills/in-progress/browser-review
Command: npx skills add https://github.com/reddb-io/red-skills --skill browser-review-reddb-io

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @reddb-io/browser-bridge.

What problem does it solve? Reviewing UI work through screenshots and prose descriptions is imprecise — the human says "the button looks off" and the agent guesses which element and what to change. This Skill replaces that loop with a live CLI-to-browser bridge where the human annotates the exact DOM element and character range, and a layout-audit gate blocks declaring work done on a broken render. ## Core Features & Use Cases - Precise element annotation: The human right-clicks the offending node in a rendered HTML artifact; the bridge captures its CSS selector, an optional text range with quote, and the comment, which the agent polls and acts on. - Layout-audit gate: assertLayoutClean throws on horizontal overflow, clipped text, or overlapping text, so a broken render cannot be marked done until fixed and re-audited. - Local and portable: All state lives under .red/browser-bridge/ on the local machine; the injected SDK is inert without the bridge server, and stripBridgeSdk recovers the byte-exact original artifact. - Use Case: After generating a prototype page, open it for review, let the human annotate the exact misaligned heading, fix it, then run the layout gate to confirm no overflow or clipped text before shipping. ## Quick Start Open my generated report.html for live browser review, collect my annotations on specific elements, and verify the layout passes the audit before calling it done.

Frequently Asked Questions about browser-review

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

FAQPage Schema
How do I get precise feedback on specific HTML elements during UI review?▼

Open the HTML artifact with openArtifact, which injects a feedback SDK and starts a local bridge server. The human right-clicks any element in the browser, and the bridge captures its CSS selector, character range, and comment for the agent to poll and act on.

How to verify a rendered page has no layout bugs before marking UI work done?▼

Collect a layout snapshot from the rendered DOM and call assertLayoutClean. It throws a LayoutAuditError on horizontal overflow, clipped text, or overlapping text, blocking completion until the render is fixed and re-audited.

Does the browser bridge send my HTML artifacts to an external server?▼

No, the bridge is fully local. All session state and annotations live under .red/browser-bridge/ on the machine, and the server is a loopback long-poll server, so nothing leaves the local environment.

What layout issues does the layout audit detect?▼

The audit detects three finding types: horizontal-overflow where content extends past the viewport width, clipped-text where content is cut off by overflow hidden or clip, and text-overlap where two text boxes collide. Scrollable overflow is not flagged.

Will the injected bridge SDK change how my HTML artifact renders?▼

No, the injected SDK is additive and self-guarding. Opened in a plain browser with no bridge running it stays inert, so the augmented file renders identically to the original, and stripBridgeSdk recovers the byte-exact source.