qa

Automate web app QA testing and fix bugs with atomic commits.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/jonkiky/ccdi-federation-ai --skill qa-jonkiky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/jonkiky/ccdi-federation-ai/tree/main/.agents/qa
Command: npx skills add https://github.com/jonkiky/ccdi-federation-ai --skill qa-jonkiky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".

Core Features & Use Cases

  • Automated end-to-end QA testing across web interfaces and APIs.
  • Generates patch commits for each bug fix and re-verifies health scores.
  • Supports tiered testing (Quick, Standard, Exhaustive) with structured reports.
  • Use Case: When a feature is requested, run QA, locate defects, fix them with atomic commits, and re-run validations until ship-readiness.

Quick Start

Run a quick QA pass on the current web app to identify high-priority bugs and push fixes.

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 fix bugs in my web application?

Automate QA testing by running systematic checks across web interfaces, then iteratively fix bugs through atomic commits. The process re-verifies health scores after each patch, providing before/after reports and a final ship-readiness summary.

What is the difference between quick, standard, and exhaustive regression testing?

Regression testing tiers filter bugs by severity: Quick checks critical and high-priority issues, Standard adds medium severity, and Exhaustive includes cosmetic defects. Each tier produces structured reports with health scores and fix evidence.

Can I run a health check on my web app without applying source code patches?

Yes, you can run report-only mode to perform a health check without modifying source code. This mode identifies bugs and generates health scores, but skips the iterative patch generation and atomic commit process.

How does automated bug fixing verify that defects are actually resolved?

Automated bug fixing verifies defects by generating a patch commit for each fix and immediately re-running validations. It calculates before and after health scores to confirm the issue is resolved before moving to the next bug.

When should I use automated test orchestration for web applications?

Use automated test orchestration when a feature is ready for testing or you need to find bugs and fix what's broken. It systematically tests web interfaces and APIs, applying atomic commits until the application reaches ship-readiness.

Does automated QA testing work for both web interfaces and APIs?

Yes, automated QA testing supports end-to-end testing across both web interfaces and APIs. It orchestrates tests, generates patches for located defects, and re-verifies health scores to ensure comprehensive coverage.