skills.rest
mopeyjellyfish
mopeyjellyfishCOMMUNITY
Explore all skills by this author →
GitHub

browser-test

Generate reproducible Playwright browser tests with evidence artifacts for UI changes.

1|Updated Apr 18, 2026
Search Tags:#workflow#testing#evidence#playwright#browser#proof
One-click install
npx skills add https://github.com/mopeyjellyfish/flywheel --skill browser-test-mopeyjellyfish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-test
Source: https://github.com/mopeyjellyfish/flywheel/tree/main/skills/browser-test
Command: npx skills add https://github.com/mopeyjellyfish/flywheel --skill browser-test-mopeyjellyfish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Proves browser-visible changes by generating reproducible, evidence-backed browser proof using Playwright.

Core Features & Use Cases

  • Browser-proof validation: run targeted Playwright-based checks to confirm UI behavior.
  • Evidence capture: collect artifacts (screenshots, traces) for review and commit.
  • Use Case: When a feature changes visible behavior, run the browser-proof workflow to validate and hand off evidence to PR review.

Quick Start

Run the browser-proof workflow against the target surface and capture the verified browser evidence with Playwright.

Frequently Asked Questions about browser-test

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

FAQPage Schema
How do I prove browser UI changes with Playwright for a pull request?▼

You prove browser UI changes by running reproducible Playwright checks that validate visible behavior and capture evidence artifacts like screenshots for PR review. This workflow confirms the observable surface changed as intended.

What is browser-proof validation and when do I need it?▼

Browser-proof validation confirms UI behavior by capturing reproducible evidence like screenshots and traces. You need it when a feature changes visible behavior and must be validated before code review.

Do I need the Playwright CLI installed to capture browser test evidence?▼

Yes, you need the Playwright CLI installed to capture browser test evidence. The workflow requires it to run targeted checks against the repo-proven target surface and generate evidence artifacts for review.

How do I capture screenshots and traces as evidence for UI navigation changes?▼

You capture screenshots and traces by running the Playwright-based workflow against the repo-proven target surface. This collects the artifacts needed to verify navigation or dynamic content changes for PR handoff.

Can I validate dynamic content changes using browser-proof workflows?▼

Yes, you can validate dynamic content changes using browser-proof workflows. The workflow applies Playwright checks to any observable surface, including dynamic content, to ensure behavior is verified before review.

What is the best way to hand off verified browser evidence to PR review?▼

The best way to hand off verified browser evidence to PR review is by running the browser-proof workflow. It generates reproducible, evidence-backed artifacts that confirm the UI changes for reviewers.

Related Skills

Explore More Software Engineering Skills→
corezoidcorezoid
58

simulator-init

Initialize and configure the Simulator.Company environment with OAuth authentication and .env storage.

Official
Intermediate
auldsyababuaauldsyababua
6

pr-backlog-cleaner

Triage, rebase, and verify GitHub pull requests for safe disposition.

Community
Advanced
patricio0312revpatricio0312rev
5

visual-regression-tester

Automate visual regression testing of web applications in CI.

Community
Advanced
timbuchingertimbuchinger
1

webapp-testing

Automate local web app verification with Python Playwright and server orchestration.

Community
Intermediate