qa

Automates web application QA testing with health scores and ship-readiness summaries.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Intension-us/attention-diagnostic --skill qa-intension-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/Intension-us/attention-diagnostic/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/Intension-us/attention-diagnostic --skill qa-intension-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates QA testing of a web application to systematically identify and verify bugs and track fixes with evidence.

Core Features & Use Cases

  • Automated QA testing across tiers (Quick, Standard, Exhaustive) with health score and ship-readiness outputs.
  • Iterative bug fixing with atomic commits and re-verification to ensure high quality.
  • Report-only mode support via /qa-only and thorough evidence generation for stakeholders.

Quick Start

Run the qa skill to test the current app, fix the discovered bugs atomically, and re-verify until ship-ready.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate web application testing to identify and fix bugs?

Automated web application testing identifies bugs by systematically executing QA campaigns, applying iterative fixes through atomic commits, and re-verifying results. It generates before and after health scores with fix evidence to track ship-readiness.

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

Quick, Standard, and Exhaustive QA testing tiers provide progressively deeper bug identification and verification coverage. Each tier produces a health score and ship-readiness summary, allowing you to balance testing thoroughness against time constraints based on your release requirements.

Can I generate QA reports without automatically applying code fixes?

Yes, you can generate QA reports without applying code fixes by using the report-only mode. This mode performs bug identification and produces thorough evidence with health scores for stakeholders, leaving the codebase untouched while still evaluating ship-readiness.

How do atomic commits work during the iterative bug fixing process?

Atomic commits isolate each bug fix into a separate, self-contained commit during the iterative fixing process. This approach systematically tracks individual fixes and re-verifies them independently, ensuring high quality and providing clear fix evidence for stakeholders.

Does automated QA testing support bash scripts and web search for verification?

Automated QA testing supports deterministic tasks using Bash, Read, Write, Edit, Glob, Grep, and WebSearch. These tools load operational instructions, execute test commands, and collect results to systematically verify bugs and generate ship-readiness summaries.