qa-only

Runs report-only QA tests on a web application and generates a structured health score, screenshots, and repro steps.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/JeremiahEllington/NoahEllington --skill qa-only-jeremiahellington
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/JeremiahEllington/NoahEllington/tree/main/.claude/skills/qa-only
Command: npx skills add https://github.com/JeremiahEllington/NoahEllington --skill qa-only-jeremiahellington

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to run comprehensive QA tests on a web application and produce a structured report with a health score, screenshots, and reproducible steps, without applying any fixes.

Core Features & Use Cases

  • Report-only testing: Systematically tests the app and surfaces defects without making changes.
  • Evidence-rich reports: Health score, screenshots, and step-by-step repros for each issue.
  • Proactive guidance: Suggests potential issues for future follow-up when asked.
  • Use cases include quick validation of a new release, regression checks on critical flows, and documentation-ready bug reports for handoff.

Quick Start

Run a report-only QA pass against the target URL and export a structured bug report with evidence.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I run QA testing on a web application and generate bug reports without applying fixes?

Report-only QA testing systematically executes tests against a web application to surface defects and generate structured bug reports without applying any code fixes. It outputs a health score, screenshots, and step-by-step repro instructions for each issue.

What is included in an automated QA health score report for web applications?

An automated QA health score report includes a calculated health score, captured screenshots, and detailed repro steps for each identified bug. It provides documentation-ready evidence for handoff without altering the application code.

Do I need a Bash-driven workflow to execute repro steps for bug reports?

Yes, a Bash-driven workflow is required to drive test execution, evidence collection, and report generation. The testing process relies on Bash commands to automate the systematic validation of web application flows.

Can I run regression checks on critical flows and just report bugs?

Yes, you can run regression checks on critical flows to just report bugs. The process proactively suggests potential issues for future follow-up and outputs structured bug reports without making any changes to the application.

What's the best way to document reproducible steps for a bug report handoff?

The best way to document reproducible steps for a bug report handoff is using report-only QA testing. It systematically captures evidence and generates documentation-ready bug reports with screenshots and step-by-step repros.

Why use report-only QA testing instead of automated testing with fixes?

Use report-only QA testing instead of automated testing with fixes when you need quick validation of a new release or unbiased defect surfacing. It separates bug discovery from resolution, providing a structured health score and evidence without modifying code.