browse-qa

Run browser-based smoke tests to verify shipped plans and generate QA reports.

6|1|Updated Mar 15, 2026

Search Tags:#automation #qa #browser-testing #pr-description #post-plan #browse-qa

Ready to run

npx skills add https://github.com/anasstissir/lenshub --skill browse-qa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse-qa
Source: https://github.com/anasstissir/lenshub/tree/main/skills/browse-qa
Command: npx skills add https://github.com/anasstissir/lenshub --skill browse-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Post-plan QA smoke testing with a headless browser verifies that shipped features match the plan and produces a paste-ready QA report for PR descriptions and GitHub issues.

Core Features & Use Cases

Navigate the app to validate core flows touched by a plan.
Generate a structured QA report suitable for PR descriptions or GitHub issues.
Provide evidence (screenshots or exact repro steps) for each finding.

Quick Start

Run a post-plan smoke test against the target URL to verify shipped features and generate a paste-ready QA report.

Frequently Asked Questions about browse-qa

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

FAQPage Schema

What is post-plan QA smoke testing with a browser?▼

Post-plan QA smoke testing with a browser verifies that shipped features match planned outcomes by navigating core app flows. It validates functionality after development and generates structured evidence like screenshots or repro steps for each finding.

How do I generate a QA report for a PR description?▼

To generate a QA report for a PR description, run a browser-based smoke test against the target URL to verify shipped features. The test navigates core flows touched by the plan and outputs a paste-ready structured report.

Do I need a browser automation environment to run post-plan reviews?▼

Yes, you need a browser automation environment to run post-plan reviews. The smoke test relies on browser tools like WebFetch and Agent to navigate the app, verify core flows, and collect evidence such as screenshots for the QA report.

Can I use browser checks to verify demo prep for shipped features?▼

Yes, you can use browser checks to verify demo prep for shipped features. The smoke test navigates the app to validate core flows touched by a plan, ensuring the features work as intended before a demonstration.

What's the best way to verify if shipped features match the planned outcomes?▼

The best way to verify if shipped features match planned outcomes is running a browser-based smoke test. It focuses on core flows touched by the plan, providing exact repro steps or screenshots to confirm the implementation matches the original specifications.

Why does my smoke test need tools like Glob and Grep to validate core flows?▼

Your smoke test needs tools like Glob and Grep to search and read project files during post-plan reviews. These tools help identify planned outcomes and verify that the shipped code matches the expected core flows before generating the final QA report.