qa

Run tiered web application tests, apply atomic fixes, and generate ship-readiness summaries.

37|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/DariusCorvus/iqualize --skill qa-dariuscorvus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/DariusCorvus/iqualize/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/DariusCorvus/iqualize --skill qa-dariuscorvus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA workflows are often ad-hoc, leading to inconsistent bug fixes and slower shipping. This Skill coordinates end-to-end QA, enabling systematic testing, atomic code fixes, and re-verification to ensure quality before release.

Core Features & Use Cases

  • End-to-end QA workflow: run tests, identify issues, apply atomic commits, re-verify, and publish ship-readiness summaries.
  • Tiered testing: Quick (critical/high), Standard (including medium), Exhaustive (cosmetic) to balance speed and assurance.
  • Evidence and health reporting: before/after health scores, fix evidence, and ship-readiness summaries, with a /qa-only mode for report-only operation.
  • Proactive suggestions: recommend testing focus when asked if a feature is ready for testing.

Quick Start

Run a test-and-fix cycle on the current web application.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate web app bug fixes with atomic commits during QA testing?

Automated QA testing identifies bugs in your web app and applies fixes using atomic commits. The workflow runs tests, edits code, and re-verifies changes to ensure each fix is isolated and validated.

What is ship-readiness reporting in an automated QA workflow?

Ship-readiness reporting calculates before and after health scores to verify application stability. It generates fix evidence and a summary confirming your web app passes critical, medium, and cosmetic test tiers.

How do I balance test coverage and speed for web application testing?

You balance coverage and speed using tiered testing: Quick for critical issues, Standard for medium severity, and Exhaustive for cosmetic bugs. This ensures appropriate assurance levels without unnecessary delays.

Can I generate a QA report without automatically applying code fixes?

Yes, you can generate a QA report without fixes by using a report-only mode. This operates by running tests and calculating health scores without modifying your codebase or creating atomic commits.

Does the QA testing workflow support proactive suggestions for feature readiness?

Yes, the workflow supports proactive suggestions. When asked if a feature is ready, it analyzes the web app and recommends specific testing focus areas to prioritize during your validation cycle.

What tools are used to orchestrate test runs and apply code edits?

The workflow uses Bash, Read, Write, Edit, Glob, Grep, and WebSearch to orchestrate tests and apply code edits. These utilities execute commands, search codebases, and modify files to resolve identified bugs.