qa

Automate Playwright browser testing against feature specs and generate QA reports.

2|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/ByeongminLee/nextjs-claude-code --skill qa-byeongminlee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/ByeongminLee/nextjs-claude-code/tree/main/template/.claude/skills/qa
Command: npx skills add https://github.com/ByeongminLee/nextjs-claude-code --skill qa-byeongminlee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI-driven browser testing automates validation of feature specs by executing real user interactions in a browser, reducing manual QA effort and increasing test coverage.

Core Features & Use Cases

  • Spec-driven testing: Reads feature specs and navigates a real browser to verify REQs end-to-end.
  • Versatile modes: Supports quick smoke tests, full spec-driven runs, E2E test file execution, visual regression, and accessibility audits.
  • Use Case: A product engineer uses /qa to automatically validate a new checkout flow against its spec before release.

Quick Start

Run /qa with a feature name to start automated, spec-driven browser testing against that feature.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate spec-driven browser testing for new features?

Automated spec-driven browser testing reads your spec files and uses Playwright to execute real user interactions in a browser. It validates feature requirements end-to-end, runs visual and accessibility checks, and outputs a structured QA report without modifying source code.

Can I run visual regression and accessibility audits with Playwright?

Yes, AI-driven browser testing with Playwright supports visual regression and accessibility audits alongside spec-driven test flows. It executes these checks in real browsers to validate feature requirements and reports the results structurally.

What is the best way to validate a new checkout flow against its spec before release?

Spec-driven browser testing validates a new checkout flow by reading feature specs and executing real user interactions in a browser via Playwright. It verifies requirements end-to-end, runs visual and accessibility checks, and generates a structured QA report.

Does spec-driven QA testing modify my source code during validation?

No, spec-driven QA testing does not modify your source code. It strictly reads spec.md and design.md files, coordinates Playwright browser-tester agents to execute deterministic test flows, and outputs a structured QA report without altering the codebase.

How do I execute E2E test files and smoke tests in a real browser environment?

AI-driven Playwright testing executes E2E test files and smoke tests in a real browser environment. It supports versatile testing modes including quick smoke tests, full spec-driven runs, and E2E test file execution to validate feature requirements.