qa

Automate browser-based QA workflows to detect bugs and generate regression tests.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/0xHarbs/agent-setup --skill qa-0xharbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/0xHarbs/agent-setup/tree/main/claude/skills/lifecycle/qa
Command: npx skills add https://github.com/0xHarbs/agent-setup --skill qa-0xharbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browser-based QA that finds bugs, fixes them, and writes regression tests.

Core Features & Use Cases

  • Automate browser-based QA workflows to verify app behavior, detect regressions, and generate regression tests.
  • Supports three modes: diff-aware, full, and quick smoke tests; reads the QA map from /qa-map to structure testing.
  • Enables targeted validation of UI flows and end-to-end checks across web apps.

Quick Start

Run the /qa workflow to begin diff-aware testing on your app and review the generated regression tests.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate browser regression tests for my web app?

Automate browser regression tests by running the /qa workflow to verify app behavior, detect bugs, and automatically generate regression tests. It structures testing by reading the QA map from /qa-map to validate UI flows.

What is diff-aware testing and when should I use it for QA workflows?

Diff-aware testing targets only the areas of your web app affected by recent changes. Use it during active development for faster validation, while full mode tests everything and quick mode runs rapid smoke tests.

Do I need a QA map to run automated browser testing workflows?

Yes, you need a QA map placed at /qa-map to structure the automated browser testing. The workflow reads this map to determine how to validate UI flows and execute end-to-end checks across your application.

What's the best way to verify UI fixes and catch regressions in browser workflows?

The best way to verify UI fixes is using an automated QA workflow that identifies bugs, confirms fixes, and writes regression tests. It enforces robust tooling requirements for reliable end-to-end verification across web apps.

Can I run quick smoke tests instead of full browser QA checks?

Yes, you can run quick smoke tests instead of full checks. The QA workflow supports three modes: diff-aware for targeted checks, full for comprehensive testing, and quick for rapid smoke testing of your web app.