qa-only

The qa-only skill is a report-only quality assurance testing workflow for web applications. It is designed for situations where the goal is to test an application, identify issues, and produce a structured QA report without making any code changes or fixes. This makes it appropriate when a user explicitly wants bug reporting only, such as requests to "just report bugs," "qa report only," or "test but don't fix." The skill focuses on documenting the current health of the application rather than resolving defects, which helps teams separate testing from remediation.

Its documented capabilities include systematically testing a web application and producing a structured report. That report includes a health score, screenshots, and reproducible steps for identified issues. The skill also includes behavior controls tied to its runtime preamble, such as respecting a configuration that disables proactive skill suggestions unless the user explicitly asks. In addition, the skill includes setup and onboarding behaviors related to upgrade handling, a one-time completeness-principle introduction, and a one-time telemetry preference prompt. These operational steps are part of how the skill is run, but the core functional outcome remains QA reporting only, with no fixing behavior.

This skill is intended for users who need a formal bug report without any code modifications, including developers, QA engineers, reviewers, or project stakeholders who want an assessment of application quality. It is especially useful in workflows where testing and fixing are intentionally separated, or where a user wants documentation of issues before deciding on remediation. When a full test-fix-verify loop is needed instead, the content explicitly directs users to use /qa rather than qa-only.