skills.rest
paycrux
paycruxOFFICIAL
Explore all skills by this author →
GitHub

qa

Automate implementation verification with a headless browser guided by task-plan files.

Updated Mar 30, 2026
Search Tags:#automation#testing#qa#verification#bug-reporting#headless-browser
One-click install
npx skills add https://github.com/paycrux/ai-skills --skill qa-paycrux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/paycrux/ai-skills/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/paycrux/ai-skills --skill qa-paycrux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

task-plan 문서를 기반으로 browse(헤드리스 브라우저)를 사용해 구현 결과를 검증합니다. 버그를 발견하면 리포트를 작성하고, 즉시 수정할지 사용자에게 확인합니다. 이후 /implement로 연결합니다.

Core Features & Use Cases

  • Automated validation of implementation results via headless browser
  • Integrated bug reporting and immediate verification
  • Linkage to /implement for fixes

Quick Start

Run the QA workflow by pointing /qa at your task-folder or URL to begin automated validation and bug reporting.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate verification of implementation results using a headless browser?▼

Automated verification of implementation results uses a headless browser guided by a task-plan to test your application, extract test-scopes, and generate structured bug reports for immediate re-verification.

What is a task-plan based QA workflow?▼

A task-plan based QA workflow defines test scopes within docs task-plan files or direct URLs, driving a headless browser to validate implementations, generate replayable evidence, and trigger fixes.

How does bug reporting work when a headless browser test fails?▼

Bug reporting during headless browser testing generates structured evidence with guardrails, immediately re-verifying the implementation and prompting the user before linking to an implement workflow for fixes.

Can I run automated QA validation directly against a URL instead of a task-plan file?▼

Yes, automated QA validation accepts direct URLs as input, applying the same headless browser testing, test-scope extraction, and replayable bug reporting workflows used for task-plan files.

What are the limitations of headless browser QA for implementation testing?▼

Headless browser QA limitations include dependency on task-plan files or URLs for scope extraction, requiring user confirmation before triggering fixes, and generating structured evidence strictly within defined guardrails.

Do I need specific dependencies to run automated QA with a headless browser?▼

No specific dependencies are required to run automated QA with a headless browser; the workflow operates independently using task-plan files or URLs to perform validation and bug reporting.

Related Skills

Explore More Software Engineering Skills→
jacardljacardl

dogfood

Automate exploratory QA testing of web applications with a browser toolset.

Community
Advanced
multiversxmultiversx
12

fix_verification

Verify smart contract bug fixes by running Mandos scenarios and regression tests.

Official
Intermediate
tsenseitsensei
3

gstack

Drive a headless browser to interact with UI and capture annotated screenshots and diffs.

Community
Advanced
joeylife94joeylife94

qa-only

Run automated QA tests on web applications and generate detailed reports.

Community
Advanced