qa-only

Generate structured health scores, evidence, and repro steps for web applications.

10|3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/olaafrossi/FoamPilot --skill qa-only-olaafrossi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/olaafrossi/FoamPilot/tree/main/.claude/skills/qa-only
Command: npx skills add https://github.com/olaafrossi/FoamPilot --skill qa-only-olaafrossi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Non-intrusive QA testing that outputs a structured health report with evidence, screenshots, and reproducible steps without applying fixes.

Core Features & Use Cases

  • Generate health scores, evidence, and reproducible steps for web apps
  • Use in bug triage, release validation, or CI checks without code changes
  • Provide ready-to-share reports for stakeholders and developers

Quick Start

Invoke the qa-only skill to generate a report-only QA run for the current web application.

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 health report for a web application without modifying any code?

Report-only QA testing generates a structured health score, evidence, and reproducible steps for web apps without applying fixes. It performs deterministic checks and captures screenshots to validate application health non-intrusively for release validation.

Can I run non-intrusive QA checks in a CI pipeline to validate release readiness?

Yes, report-only QA testing supports CI contexts by orchestrating deterministic checks that output structured health reports. It validates release readiness and provides bug reproduction steps without altering your application codebase or applying fixes.

What is the best way to capture bug reproduction steps and evidence for web app triage?

Report-only QA testing captures screenshots and compiles reproducible steps into a structured health report for bug triage. It provides ready-to-share evidence for stakeholders and developers without modifying the application state.

Does report-only web app testing require any specific environment setup or dependencies?

Report-only QA testing requires Bash, Read, Write, AskUserQuestion, and WebSearch capabilities to orchestrate deterministic checks and capture screenshots. No external dependencies are needed beyond these standard execution environment tools for web validation.

How does non-intrusive QA testing differ from automated web testing tools that apply fixes?

Report-only QA testing strictly generates health scores, evidence, and reproducible steps without applying code fixes. Unlike automated repair tools, it provides non-intrusive validation and ready-to-share reports for stakeholders during bug triage or release validation workflows.