qa

Invoke the qa skill on your feature branch or with a target URL. It opens the app in a real browser, explores pages, tests forms and interactive elements, documents issues with screenshots, then fixes confirmed bugs and re-verifies each fix.

Diff-aware mode analyzes your branch diff with git to identify affected pages and routes, then scopes browser testing to just those changes. It cross-references commit messages to verify the change does what was intended and checks adjacent pages for regressions.

The health score is a weighted average of category scores: functional 20%, console and UX 15% each, links, visual, and performance 10% each, accessibility 15%, and content 5%. Each category starts at 100 and deducts points per issue by severity.

Yes. It detects the framework during the orientation phase and applies framework-specific checks, such as hydration errors for Next.js, CSRF tokens and Turbo behavior for Rails, and plugin conflicts for WordPress. Generic SPA guidance covers React, Vue, and Angular.

It never types credentials itself. When a sign-in wall, 2FA prompt, or CAPTCHA appears, it pauses and asks you to complete the step in the browser, then resumes testing with your authenticated session.

It tests as a user without reading source code, so it cannot verify internal logic directly. Mutating actions on non-local sites require explicit consent, and it never signs you out or switches accounts on its own.