qa-only

Explore web application pages and interactions to identify and document bugs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of testing web applications to identify and report bugs without making any code changes, providing a clear overview of application health.

Core Features & Use Cases

  • Systematic Testing: Explores web applications like a user, clicking through pages and interactions.
  • Automated Reporting: Generates detailed reports including screenshots, console errors, and step-by-step reproduction instructions for identified issues.
  • Use Case: After deploying a new feature, use this Skill to perform a thorough QA pass, documenting any regressions or new bugs found without altering the codebase.

Quick Start

Run a full QA report on the current application at http://localhost:3000.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I automate regression testing for a web application without changing the codebase?

Automated regression testing for a web application is performed by systematically exploring pages and interactions to document bugs. This Skill identifies issues with evidence like screenshots and console logs without altering the code.

What is report-only QA testing and how does it work?

Report-only QA testing is the process of identifying and documenting application bugs with evidence like screenshots and console logs without attempting to fix them. It works by systematically exploring web application pages and user interactions.

Can I automatically detect affected pages for QA testing based on code changes in a feature branch?

Yes, you can automatically detect affected pages for QA testing based on code changes in feature branches. This allows targeted regression testing by focusing only on the areas of the web application modified by recent commits.

How do I generate bug reports with screenshots and console logs for a local web application?

You can generate detailed bug reports with screenshots and console logs by running a full or quick QA pass on a local web application. The report includes step-by-step reproduction instructions for identified issues.

Does this QA testing approach modify my source code when it finds a bug?

No, this QA testing approach does not modify your source code when it finds a bug. It strictly reports bugs and documents them with evidence, leaving the codebase completely untouched.