fixme-browser-verify

Automate browser-based verification of code changes against a live dev server.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/denis-pingin/fixme --skill fixme-browser-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixme-browser-verify
Source: https://github.com/denis-pingin/fixme/tree/main/.claude/skills/fixme-browser-verify
Command: npx skills add https://github.com/denis-pingin/fixme --skill fixme-browser-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that code changes actually fix reported bugs by performing automated browser-based verification against a live development server. It validates that the bug symptom is resolved and that the expected behavior is preserved, without modifying the source code.

Core Features & Use Cases

  • Automated, browser-based verification against a running dev server to confirm bug fixes.
  • Generation of a verification report and evidence assets (screenshots, console and network logs) for QA and reproducibility.
  • Suitable for QA, release validation, and regression checks across environments.

Quick Start

Run the browser verification workflow against your dev server to produce a verification report and evidence.

Frequently Asked Questions about fixme-browser-verify

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

FAQPage Schema
How do I automate browser verification for bug fixes against a dev server?

Automated browser verification executes a live dev server to validate that code changes resolve reported bug symptoms and preserve expected behavior without modifying source code. It uses a phase-driven workflow with Playwright commands to produce a verification report and evidence assets.

Can I generate a visual regression report with screenshots and logs using Playwright?

Yes, visual regression verification generates a comprehensive report and evidence assets including screenshots, console logs, and network logs. These outputs ensure QA reproducibility and validate that bug fixes do not introduce visual regressions across environments.

Does browser-based bug fix validation require modifying the source code?

No, browser-based bug fix validation requires no source modification. It operates by running a live development server and applying a phase-driven workflow using Playwright commands to verify that the reported symptoms are resolved and expected behavior remains intact.

What is the best way to validate QA automation and release workflows across environments?

The best way to validate QA automation and release workflows is using automated browser-based verification. It executes a dev server, checks that bug fixes hold, and generates a verification report with evidence assets suitable for regression checks across environments.

How does automated browser verification work for release validation?

Automated browser verification works by executing a live dev server, validating that bug symptoms are resolved, and confirming expected behavior remains intact. It produces a verification report and evidence assets for QA and reproducibility during release validation.

When should I use automated browser verification instead of manual testing?

Automated browser verification should be used for QA, release validation, and regression checks where visual and interaction verification across environments is required. It automates the validation of bug fixes against a running dev server and produces reproducible evidence assets.