qa-only

Tests web applications and generates structured bug reports without applying fixes.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill qa-only-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/adamtpang/summon.company/tree/main/.claude/skills/qa-only
Command: npx skills add https://github.com/adamtpang/summon.company --skill qa-only-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often need an objective assessment of a web application's quality without immediately changing code. This Skill systematically tests a web app and produces a structured report with a health score, screenshots, and reproduction steps, while guaranteeing no fixes are applied. ## Core Features & Use Cases - Report-Only QA Testing: Systematically exercises a web application and documents every bug found, with zero code modifications. - Structured Bug Reports: Produces a health score, screenshots, and step-by-step reproduction instructions for each issue. - Session-Aware Workflow: Adapts behavior for interactive, headless, and spawned sessions, with decision briefs for user choices. - Use Case: Before a release, ask for a QA pass on your staging site. You receive a prioritized bug report with screenshots and repro steps that engineers can triage, while the codebase remains untouched. ## Quick Start Ask the assistant to run a report-only QA pass on your web app and list every bug found with screenshots and repro steps, without fixing anything.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I test a web app without changing any code?

Invoke the qa-only skill, which systematically tests the web application and produces a structured report with a health score, screenshots, and reproduction steps. It never modifies source files, making it safe to run against any branch or environment.

What is the difference between qa-only and a full QA workflow?

qa-only stops at reporting: it finds bugs and documents them but never fixes anything. The full /qa skill runs a test-fix-verify loop that also patches the code, so use qa-only when you only want a bug report.

What does the QA report include?

The report contains an overall health score for the application, screenshots captured during testing, and step-by-step reproduction instructions for each bug found. This gives engineers everything needed to triage and fix issues later.

Can qa-only run in headless or CI environments?

Yes. The skill detects the session kind (interactive, headless, or spawned) and adapts. In headless runs it blocks rather than prompting when a question cannot be answered, and in spawned sessions it auto-chooses recommended options and reports results as prose.

When should I not use report-only QA testing?

Avoid it when you want issues fixed immediately, since qa-only never touches code. If you need the full test-fix-verify loop, use the /qa skill instead, which applies and verifies fixes after finding bugs.