qa-only

Test a web application and generate a QA report with health score, screenshots, and repro steps.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/onlypfachi/chief --skill qa-only-onlypfachi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/onlypfachi/chief/tree/main/qa-only
Command: npx skills add https://github.com/onlypfachi/chief --skill qa-only-onlypfachi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams want to validate a web application and surface issues without applying fixes. This Skill delivers a report-only QA flow that outputs a structured bug report, health score, and visual evidence so stakeholders can review issues without modifying the codebase.

Core Features & Use Cases

  • Systematically tests a web application and generates a structured QA report with health score, screenshots, and repro steps.
  • When asked to "qa report only" or "test but don't fix", it operates in a no-fix mode; for full test-fix-verify, use /qa.
  • Real-world scenario: QA a new feature on a staging URL and produce a report to hand to developers.

Quick Start

Tell the system to run a report-only QA pass and generate a structured bug report.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I generate a QA report for a web app without applying any code fixes?

A report-only QA pass validates a web application by producing a structured bug report with health scores, screenshots, and repro steps while avoiding any code changes. This lets stakeholders review issues without modifying the codebase.

What is included in an automated web application testing report?

An automated web application testing report includes a health score, visual evidence via screenshots, and detailed repro steps for targeted pages and interactions. It provides clear severity labeling to help developers understand and prioritize the issues.

How do I test a staging URL and produce a structured bug report for developers?

You can systematically test a staging URL to produce a structured bug report by running a report-only QA pass. It captures visual evidence and repro steps, creating a handoff document for developers without altering the code.

Do I need browser automation to capture screenshots and repro steps for QA testing?

Yes, browser automation is expected to run this QA testing flow. It supports evidence capture like screenshots and maps out repro steps for targeted interactions, enabling a comprehensive validation report without applying fixes.

What is the difference between report-only QA testing and full test-fix-verify?

Report-only QA testing surfaces issues and generates a structured report without modifying code, whereas full test-fix-verify applies changes. Use report-only mode when asked to test but not fix, and the full flow when remediation is needed.