gxpm-browser

Automate headless browser QA evidence capture with Playwright commands.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/laozhong86/gxpm --skill gxpm-browser
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: gxpm-browser
Source: https://github.com/laozhong86/gxpm/tree/main/skills/gxpm-browser
Command: npx skills add https://github.com/laozhong86/gxpm --skill gxpm-browser

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

This skill enables reliable QA evidence capture using a headless browser to reproduce user-visible issues, generate screenshots, and verify DOM state within the gxpm workflow.

Core Features & Use Cases

  • Navigate and inspect pages to verify titles, final URL, and render state during QA gates.
  • Capture screenshots and DOM-level assertions to support verify-findings and issue validation.
  • Reuse authenticated sessions via storage-state to accelerate repeated tests without re-login.

Quick Start

Use the gxpm-browser skill during the QA phase to capture browser evidence (screenshots, DOM assertions, and form interactions) for issue verification.

Frequently Asked Questions about gxpm-browser

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

FAQPage Schema
How do I automate browser screenshot capture for QA evidence?โ–ผ

Automating browser screenshot capture for QA evidence uses a headless browser to navigate web pages and record visual proof. This skill drives Playwright to capture screenshots, verify DOM state, and log interactions during QA gates to reproduce user-visible issues.

Can I reuse authenticated sessions for headless browser QA testing?โ–ผ

You can reuse authenticated sessions for headless browser QA testing by leveraging storage-state persistence. This approach saves the login state, allowing repeated tests to execute without re-login, which accelerates the QA evidence capture workflow.

Does gxpm-browser require Playwright to run DOM assertions and form interactions?โ–ผ

gxpm-browser requires Playwright as its underlying engine to run DOM assertions and form interactions. The skill provides commands for navigate, assert, click, and type, relying on Playwright to automate the headless browser environment for issue verification.

What is the best way to verify web page render state during QA gates?โ–ผ

The best way to verify web page render state during QA gates is by automating headless browser navigation to inspect final URLs and titles. This skill captures DOM-level assertions and screenshots to validate issue findings and verify rendering.

Are there limitations when using a headless browser for QA evidence capture?โ–ผ

A limitation when using a headless browser for QA evidence capture is the dependency on Playwright for execution. While it automates screenshots and form interactions, complex visual rendering issues that require manual human perception may still need direct browser inspection.