rezops

Automate browser-based QA with a persistent headless browser for UI interaction and verification.

Updated Apr 22, 2026

Search Tags:#automation #qa #playwright #browser #headless #screenshot

Ready to run

npx skills add https://github.com/diiviikk5/rezops --skill rezops

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rezops
Source: https://github.com/diiviikk5/rezops/tree/main
Command: npx skills add https://github.com/diiviikk5/rezops --skill rezops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Persistent, deterministic browser automation for QA and site dogfooding. It eliminates the guesswork of manual testing by giving you a fast, persistent headless browser to load pages, interact with elements, verify state, and capture evidence.

Core Features & Use Cases

Persistent headless browser for automated QA, deployment verification, and product dogfooding.
Navigate pages, interact with elements, and verify UI state across changes.
Diff before/after, annotate screenshots, and test responsive layouts, forms, uploads, and dialogs.
Produce bug evidence and re-run steps to reproduce issues quickly.

Quick Start

Install rezops and run bun run build to generate the browser binary, then run the browse CLI to start testing a page.

Frequently Asked Questions about rezops

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

FAQPage Schema

How do I automate QA testing with a headless browser?▼

Automate QA testing with a headless browser by driving a persistent instance to load pages, interact with UI elements, verify state, and capture annotated screenshots as evidence. This approach eliminates manual guesswork and enables deterministic deployment verification.

What is persistent browser automation for product dogfooding?▼

Persistent browser automation for product dogfooding is using a continuous headless browser session to navigate pages, test responsive layouts, and verify UI state across changes. It provides deterministic, repeatable testing for real-world apps.

How do I capture annotated screenshots during automated browser testing?▼

Capture annotated screenshots during automated browser testing by driving a headless browser to interact with elements and record visual evidence. You can diff before and after states to quickly reproduce issues and produce bug evidence.

Can I test responsive layouts, forms, and dialogs in headless mode?▼

Yes, you can test responsive layouts, forms, and dialogs in headless mode by driving the persistent browser to interact with these UI components. It supports navigation and content reading to verify outcomes across different views.

Does headless browser QA testing work with Claude Code workflows?▼

Yes, headless browser QA testing integrates with Claude Code workflows to run in headless mode, capture evidence, and guide continuous QA. This allows you to automate deployment verification and product dogfooding within your existing environment.

What are the limitations of using a headless browser for QA testing?▼

Limitations of using a headless browser for QA testing include the inability to visually verify rendering in real-time and potential discrepancies between headless execution and actual user environments. It requires building the browser binary before running tests.