qa-only

Generates structured bug reports from web application QA testing without code changes.

Updated Mar 27, 2026

Search Tags:#testing #qa #regression #web-app #bug-report #repro-steps

Ready to run

npx skills add https://github.com/AlejandroFigini/artist-portfolio --skill qa-only-alejandrofigini

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/AlejandroFigini/artist-portfolio/tree/main/.agent/skills/qa-only
Command: npx skills add https://github.com/AlejandroFigini/artist-portfolio --skill qa-only-alejandrofigini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing identifies and documents defects in a web application without applying any code changes, preserving the current state while enabling thorough triage activities.

Core Features & Use Cases

Systematically perform QA passes and generate structured bug reports with reproducible steps, health scores, and evidence (screenshots) without patches.
Use cases include post-release regression checks, defect triage, and quick sanity checks where fixes should be verified later.
Proactively surface high-priority issues for engineering review without modifying source code.

Quick Start

Ask the assistant to perform a report-only QA pass on your application to generate a bug report without making any changes.

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 bug report with reproducible steps for web app regression testing?▼

Bug report generation for web app regression testing automates structured QA passes to collect reproducible steps, health scores, and evidence like screenshots without applying code changes. This preserves the current application state for thorough defect triage.

What is report-only QA testing and when do I need it for defect triage?▼

Report-only QA testing identifies and documents defects in a web application without applying patches. You need it for post-release regression checks and defect triage when testers must surface high-priority issues for engineering review without modifying source code.

Can I run manual QA checks and capture screenshots without modifying my source code?▼

Manual QA checks can systematically capture screenshots and document defects without modifying source code. The process attaches artifacts and summarizes issues while preserving the current application state for later verification.

What's the best way to perform a sanity check that surfaces high-priority issues for engineering review?▼

The best way to perform a sanity check that surfaces high-priority issues is to run an automated report-only QA pass. It systematically collects health metrics and evidence, summarizing issues for engineering review without applying any patches.

Do I need a testing harness to collect health metrics during a QA pass?▼

A testing harness is required to collect health metrics, reproduce steps, and attach artifacts during a QA pass. The harness integration enables the systematic collection of evidence needed to generate structured bug reports.

Why does this QA testing approach not apply patches or fix code during bug triage?▼

This QA testing approach does not apply patches or fix code during bug triage to preserve the current application state. It focuses entirely on documenting defects with reproducible steps and evidence so fixes can be verified later.