qa-verification

Simulate human QA in a browser to flag visual and functional issues.

1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/Porkbutts/porkbutts-n-taters --skill qa-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-verification
Source: https://github.com/Porkbutts/porkbutts-n-taters/tree/main/skills/qa-verification
Command: npx skills add https://github.com/Porkbutts/porkbutts-n-taters --skill qa-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA verification skill that tests like a human QA would — navigating the app in a browser, looking at what's on screen, and flagging anything that looks wrong. Use when verifying implemented features match task specifications, testing user flows, or validating acceptance criteria from docs/TASKS.md. Triggers on "verify this PR", "QA this feature", "visual test", "check the UI", "screenshot test", "verify task X". Works against localhost, preview/staging deployments, and production URLs. Auto-selects Google accounts; pauses for user assistance only on credential-based login flows.

Core Features & Use Cases

  • Manual-to-automated QA workflow: Validate features by walking user flows, capturing visual evidence, and documenting findings.
  • Visual inspection & consistency: Identify layout misalignments, truncated text, broken interactions, and loading issues across localhost or staging URLs.
  • Use Case: Example: verify a new checkout flow on a staging deployment by validating UI state, form validation, error messages, and performance hints.

Quick Start

To begin QA verification, specify the target URL and acceptance criteria, then run a browser-based session to navigate the app, capture screenshots, and log findings.

Frequently Asked Questions about qa-verification

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

FAQPage Schema
How do I run visual UI testing against a staging deployment?

Visual UI testing runs directly in a browser session against your staging or localhost URLs, navigating user flows to capture screenshots and flag layout issues. It simulates human QA by inspecting the screen for misalignments, broken interactions, and loading issues.

Can I verify acceptance criteria without writing new test code?

Yes, you can verify acceptance criteria without code changes by using a browser-based QA workflow. The process navigates your web app, validates UI state and form validation, and documents findings against task specifications from your docs.

What is browser-based QA verification for user flows?

Browser-based QA verification is a manual-to-automated process that validates implemented features by walking user flows like signup or checkout. It captures visual evidence and logs functional issues without requiring modifications to your application code.

Does browser QA testing handle Google account logins automatically?

Browser QA testing auto-selects Google accounts during navigation. It only pauses to require user assistance when encountering credential-based login flows, ensuring secure access while testing protected user flows.

How do I check a checkout flow for UI validation errors?

To check a checkout flow, specify the target URL and acceptance criteria to start a browser session. The verification process navigates the flow, testing UI state, form validation, error messages, and performance hints, then documents any visual or functional issues.