QA Workflow Skill

Automate end-to-end browser QA testing with Playwright and ArangoDB checks.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/stravinest/house-hold-account --skill qa-workflow-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: QA Workflow Skill
Source: https://github.com/stravinest/house-hold-account/tree/main/.claude/skills/qa-workflow
Command: npx skills add https://github.com/stravinest/house-hold-account --skill qa-workflow-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill bridges frontend and backend QA by orchestrating real-browser, end-to-end testing and automated reporting, eliminating manual test orchestration.

Core Features & Use Cases

  • End-to-end QA automation: Seamlessly connect frontend and backend to run browser-based tests without manual intervention.
  • Automatic issue resolution: Detects common blockers (server not running, missing test accounts) and resolves them automatically.
  • Auto report generation: Produces MD QA reports in the .qa-reports directory after test execution.
  • Auto-approval workflow: Runs tests and proceeds through tools without waiting for user confirmation.

Quick Start

Activate this skill with the QA Workflow commands (QA 워크플로우, /qa-workflow, QA 테스트, E2E 테스트) and ensure prerequisites are installed. Then run the tests and review the generated reports in .qa-reports.

Frequently Asked Questions about QA Workflow Skill

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

FAQPage Schema
How do I automate end-to-end browser testing with Playwright and ArangoDB?▼

End-to-end browser testing with Playwright and ArangoDB is automated by orchestrating frontend UI checks, backend validation, and database verification in a real browser without manual intervention.

Can I automatically resolve common blockers like a missing server during E2E testing?▼

Yes, E2E testing workflows can automatically detect common blockers such as a server not running or missing test accounts, and resolve them automatically to proceed with test execution.

How do I generate automated QA reports after running Playwright tests?▼

Automated QA reports are generated as Markdown files in the .qa-reports directory immediately after Playwright test execution completes, requiring no manual reporting steps.

Does this QA workflow support auto-approval execution without manual confirmation?▼

Yes, the QA workflow runs tests and proceeds through tools using an auto-approval workflow, executing the entire end-to-end testing process without waiting for user confirmation.

What is the best way to validate login and data management workflows in a real browser?▼

The best way to validate login and data management workflows is using an automated end-to-end QA workflow that connects frontend interactions with backend database checks in a real browser environment.

Do I need to manually set up test accounts before running ArangoDB data verification?▼

No, you do not need to manually set up test accounts, as the workflow detects missing test accounts and other common blockers, resolving them automatically before running database verification.