manually-validate-fix

Reproduce production bugs and confirm fixes locally via Selenium browser automation.

1.2k|114|Updated May 17, 2025
One-click install
npx skills add https://github.com/basecamp/lexxy --skill manually-validate-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manually-validate-fix
Source: https://github.com/basecamp/lexxy/tree/main/.claude/skills/manually-validate-fix
Command: npx skills add https://github.com/basecamp/lexxy --skill manually-validate-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate bug fixes in PR workflows by reproducing the bug in production and confirming the fix locally through browser automation, reducing guesswork and accelerating validation cycles.

Core Features & Use Cases

  • Reproduces production bug scenarios using a Selenium-based workflow.
  • Verifies fix applicability across environments (production vs local) with a single scripted validation approach.
  • Guides teams through plan, script, run, and verdict steps for PR validation in a deterministic manner.

Quick Start

Run the manual validation workflow against a PR to reproduce the bug and confirm the fix locally.

Frequently Asked Questions about manually-validate-fix

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

FAQPage Schema
How do I validate a bug fix in a PR using browser automation?

To validate a bug fix, you can use a Selenium-based workflow to reproduce the bug in production and confirm the fix locally through browser automation. This process guides steps from understanding the bug to a final verdict across PR workflows.

Can I reproduce a production bug locally to confirm a code fix?

Yes, you can reproduce a production bug scenario and confirm the code fix locally using a single scripted validation approach. It verifies fix applicability across environments by running browser automation tests.

Do I need Selenium WebDriver to automate manual validation of bug fixes?

Yes, this manual validation workflow requires WebDriver-based automation tooling. It relies on Selenium to load scripts or instructions from a defined URL and automate browser interactions for deterministic PR validation.

What is the standard workflow for reproducing a bug and confirming a fix?

The standard workflow for reproducing a bug and confirming a fix involves four deterministic steps: plan, script, run, and verdict. This guides teams through preparing a reproducibility plan to producing evidence of results.

What's the best way to automate QA validation for bug-fix pull requests?

The best way to automate QA validation for bug-fix pull requests is using a browser-based test workflow that reproduces the bug in production and confirms the fix locally, reducing guesswork and accelerating validation cycles.

When should I not use browser automation for PR review?

You should avoid browser automation for PR review when lacking a reproducibility plan or a defined URL for loading test scripts. Without WebDriver-based tooling and a reproducible bug scenario, the validation cannot produce deterministic evidence.