About qa-only
A report-only QA skill for testing web applications and documenting evidence without changing code, tests, or configuration. It supports scoped exploration and records findings, reproduction steps, coverage, and limitations without claiming checks that did not run.
Key features
- 01Test web applications without modifying them
- 02Follow quick, diff-aware, full, or regression scope
- 03Document issues and reproduction steps
- 04Record evidence, coverage, and limitations
- 05Write a QA report at the requested location
Use cases
- 01Verifying a requested web application change
- 02Documenting defects and reproduction evidence
- 03Reporting incomplete test coverage
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/qa-onlyin Claude Code to confirm it loaded.
Details
From the project READMEQA Report Only
Test and document the requested web application using shared exploration. The deliverable is a report and evidence; do not edit application code, tests or configuration, commit, push or merge.
Read source when needed to map a requested diff to routes or understand reproduction, including backend changes that affect user flows. Read-only source tracing is compatible with report-only QA. Use the actual verified base; do not assume main.
Follow the selected quick, diff-aware, full or regression scope. Report real findings, including zero when the evidence supports it. Do not force a quota or award untested categories a perfect score. Report unavailable browser, roles, data or checks as incomplete coverage. A healthy tested route does not establish whole-site health.
Write qa-report-<domain>-<date>.md in the requested artifact location with scope, tested coverage, issues, repro steps, evidence and limitations. Propose corrections when useful without applying them. Never claim required verification passed when it did not run.