qa-browser

Execute chrome-devtools-based browser checks to verify UI changes deterministically.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jukqaz/stack-pilot --skill qa-browser-jukqaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-browser
Source: https://github.com/jukqaz/stack-pilot/tree/main/addons/stackpilot-dev-kit/bundles/codex/skills/qa-browser
Command: npx skills add https://github.com/jukqaz/stack-pilot --skill qa-browser-jukqaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deterministic verification of UI changes across browser contexts, reducing reliance on manual live checks.

Core Features & Use Cases

  • Chrome DevTools-driven checks for state, console, network, and DOM.
  • Reproducible UI verification across multi-step flows and visual updates.
  • Use Case: When a UI change is introduced, run a repeatable verification to confirm expected behavior and render.

Quick Start

Run the qa-browser skill on the target page to execute a Chrome DevTools–driven verification.

Frequently Asked Questions about qa-browser

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

FAQPage Schema
How do I automate UI testing for multi-step UX flows?

Automate UI testing for multi-step UX flows by running Chrome DevTools-based browser checks that deterministically verify state, console, network, and DOM elements. This provides reproducible verification across feature regressions and visual updates.

What is deterministic visual regression testing for browser contexts?

Deterministic visual regression testing is a repeatable verification process that executes Chrome DevTools checks to confirm expected behavior and rendering. It reduces reliance on manual live checks by validating UI changes across routes and states.

Do I need Chrome DevTools to run deterministic browser checks?

Yes, you need Chrome DevTools to run these deterministic browser checks. The skill requires Chrome DevTools, a reproducible target page, and a defined verification plan integrated into the workflow to execute properly.

Can I verify network and console state during feature regressions?

Yes, you can verify network and console state during feature regressions using Chrome DevTools-driven checks. This allows you to deterministically validate UI changes and ensure expected render and behavior across multi-step flows.

What's the best way to set up reproducible UI verification across routes?

Set up reproducible UI verification by defining a verification plan integrated into the skill workflow, targeting a reproducible page. Run the skill to execute Chrome DevTools checks for deterministic validation across routes and visual states.