qa

Run browser-based QA checks and return a detailed issue list.

1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/jackneil/claude-jacked --skill qa-jackneil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/jackneil/claude-jacked/tree/main/jacked/data/skills/qa
Command: npx skills add https://github.com/jackneil/claude-jacked --skill qa-jackneil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Testing UI changes for visual correctness, interactions, and console errors to surface issues early and guide fixes.

Core Features & Use Cases

  • Provides targeted (qa) and thorough (ux) browser QA passes, returning a detailed issue list for planning fixes.
  • Operates in a read-only mode, generating findings without modifying code, enabling safe validation before changes.
  • Integrates with fix planning workflows via superpowers:writing-plans and verification steps like /dcr.

Quick Start

Run qa to initiate a browser-based QA pass and generate a detailed issue list for remediation.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I identify UI regressions across web pages?

Identify UI regressions by running browser-based QA checks that return a detailed issue list for planning fixes. The QA pass targets visual correctness, interactions, and console output without modifying code.

Can I run a read-only browser QA pass that does not modify my code?

Yes, browser QA operates in a read-only mode using specialized tooling to generate findings and issue reports. It validates visual correctness and interactions safely without applying any code changes.

What is the best way to triage UI bugs found during visual regression testing?

The best way to triage UI bugs is to generate a detailed issue list from the browser QA pass. This list categorizes visual and interaction findings to guide remediation and fix planning.

Does browser QA integrate with fix planning and verification workflows?

Yes, browser QA integrates with fix planning workflows via superpowers:writing-plans and verification steps using /dcr. It outputs reports that feed directly into planning fixes and subsequent verification.

What is the difference between a targeted QA pass and a thorough UX review?

A targeted QA pass focuses on specific UI regressions, while a thorough UX review covers broader pages, interactions, and console output. Both return detailed issue lists for planning fixes.