browser-smoke-review

Name: browser-smoke-review
Availability: InStock
Author: fallow

Reviews web pages and preview deployments using browser automation and screenshots.

4.4k|154|Updated Mar 17, 2026

Search Tags:#playwright #screenshot #Browser Automation #smoke test #console errors #docs review #preview deployment

Ready to run

npx skills add https://github.com/fallow-rs/fallow --skill browser-smoke-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser-smoke-review
Source: https://github.com/fallow-rs/fallow/tree/main/.agents/skills/browser-smoke-review
Command: npx skills add https://github.com/fallow-rs/fallow --skill browser-smoke-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually checking docs sites, preview deployments, and rendered output for visual or functional regressions is slow and error-prone. This Skill automates browser-based smoke testing so rendered pages are inspected, screenshotted, and checked for console or network errors.

Core Features & Use Cases

Browser Smoke Testing: Open target URLs or local previews and inspect page structure and visible content.
Screenshot Capture: Capture screenshots of rendered pages for review and documentation.
Console and Network Checks: Detect console errors and obvious network failures on web-facing surfaces.
Use Case: After deploying a docs site preview, run a browser smoke review to verify pages render correctly, capture screenshots, and report any console errors with page context.

Quick Start

Use browser automation to smoke test the docs preview URL, capture screenshots, and report any console errors or rendering issues.

Frequently Asked Questions about browser-smoke-review

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

FAQPage Schema

How do I smoke test a docs site with browser automation?▼

Open the target URL or local preview in a browser automation tool like Playwright, inspect the page structure and visible content, then check for console errors and network failures. Capture screenshots to document the rendered state for review.

How to capture screenshots of preview deployments automatically?▼

Use browser automation to navigate to the preview deployment URL and capture screenshots of the rendered pages. Screenshots provide visual evidence for review and can be attached to reports with page and path context.

Can browser smoke tests detect console and network errors?▼

Yes, browser automation can monitor the page console for errors and track network requests for obvious failures during page load. These signals are reported alongside the inspected content to surface correctness issues.

When should I use a browser smoke review instead of product feedback?▼

Use a browser smoke review when you need functional verification of rendered pages, screenshots, and error detection. If you want subjective product or UX feedback rather than smoke testing, combine it with a panel review approach.

What are the limitations of browser-based smoke testing?▼

Browser smoke tests verify visible rendering, console errors, and obvious network failures, but they do not replace deep functional or performance testing. They report surface-level UX and correctness issues rather than exhaustive coverage.