qa

Name: qa
Availability: InStock
Author: agwacom

Automate QA testing and iterative bug fixes for web applications.

Updated Mar 30, 2026

Search Tags:#automation #testing #qa #reporting #shipping #bug-fix #web-app

Ready to run

npx skills add https://github.com/agwacom/adeel --skill qa-agwacom

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/agwacom/adeel/tree/main/skills/qa
Command: npx skills add https://github.com/agwacom/adeel --skill qa-agwacom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA testing and bug fixing for web apps is manual, slow, and error-prone. This skill automates systematic QA cycles and ensures issues are resolved with traceable evidence.

Core Features & Use Cases

Automated QA passes across web applications with tiered depth (Quick, Standard, Exhaustive).
Iterative bug fixing with atomic commits and re-verification.
Ship-readiness reporting including before/after health scores and fix evidence.

Quick Start

Start a QA cycle for the active web app, run tests at the requested scope, and begin atomic bug fixes with verification after each change.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I automate QA testing and bug fixing for web applications?▼

You can automate QA testing by invoking systematic QA cycles via slash commands like /qa or /adeel:qa-only on your web app. This triggers automated testing, iterative bug fixes with atomic commits, and a ship-readiness summary with health scores.

What is the difference between Quick, Standard, and Exhaustive QA testing tiers?▼

Quick, Standard, and Exhaustive QA tiers control the depth and scope of your automated testing cycle. Each tier produces before/after health scores and fix evidence, but higher tiers perform more comprehensive verification across the web application.

How do I generate ship-readiness reports with fix evidence for my web app?▼

Ship-readiness reports are generated automatically after completing a QA cycle. They include before/after health scores, structured fix evidence, and a summary confirming whether the web application is ready for shipping.

Can I enforce atomic commits for each bug fix during automated QA cycles?▼

Yes, automated QA cycles enforce atomic commits for every individual bug fix. After each change, the system performs re-verification to ensure the fix is traceable and the web application remains stable.

How do I start a QA cycle for my active web app using slash commands?▼

Start a QA cycle by running slash commands like /qa or /adeel:qa-only in your active web app environment. This initiates testing at your requested scope and begins atomic bug fixes with verification after each change.

Does automated QA testing work without manual setup for reporting?▼

Automated QA testing handles reporting automatically without manual setup. It produces deterministic QA cycles, structured reports, before/after health scores, and fix evidence directly through the slash command invocation.