qa

Provide the target URL and choose a mode: full for systematic exploration, --quick for a 30-second smoke test, or --regression with a baseline file. The skill visits pages, interacts with elements, checks the console, and writes a structured report with screenshot evidence.

The report contains a weighted health score out of 100, the top 3 issues to fix, a console error summary, severity counts, and detailed issues with repro steps and annotated screenshots. A baseline.json is saved for future regression comparisons.

Yes. It supports credential-based login by filling the login form, importing cookies from a JSON file, and handling 2FA by asking the user for the code. Passwords are always redacted as [REDACTED] in the report.

Yes. It detects the framework automatically and applies specific guidance, such as checking hydration errors in Next.js, CSRF tokens in Rails, and using interactive snapshots for client-side navigation in SPAs.

Each category (console, links, visual, functional, UX, performance, content, accessibility) is scored 0-100 with deductions per issue severity, then combined using fixed weights. Functional issues carry the highest weight at 20 percent.

It cannot bypass CAPTCHAs without user help and does not read source code, testing only as an end user. Deep coverage depends on reachable pages, so hidden or role-restricted flows may need explicit credentials or scope instructions.