skills.rest
fghaffar
fghaffarCOMMUNITY
Explore all skills by this author →
GitHub

qa

Automate end-to-end QA testing and atomic bug fixes for web applications.

Updated Mar 25, 2026
Search Tags:#automation#testing#qa#verification#bug-fix#web-app#health-score
One-click install
npx skills add https://github.com/fghaffar/faystack --skill qa-fghaffar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/fghaffar/faystack/tree/main/qa
Command: npx skills add https://github.com/fghaffar/faystack --skill qa-fghaffar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA for web apps is often manual, slow, and error-prone. This Skill automates end-to-end QA testing and guides developers to fix bugs iteratively, reducing cycle times.

Core Features & Use Cases

  • Three tiers: Quick (critical/high), Standard (+ medium), Exhaustive (+ cosmetic), each producing before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.
  • Automatically run tests, collect results, and commit fixes atomically, then re-verify until the project passes the defined criteria.

Quick Start

Run /qa on your feature branch to start automated QA and automatically fix and verify until you’re 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 end-to-end QA testing for web applications?▼

Automated QA testing for web applications runs test suites across feature branches, collects results, and applies atomic bug fixes with re-verification until ship-readiness criteria are met. Health scores and fix evidence are generated for each cycle.

What's the best way to fix bugs iteratively during release workflows?▼

Iterative bug fixing during release workflows is handled by automatically committing atomic fixes after test failures, then re-verifying the project. This repeats until the web application passes the defined health score and ship-readiness criteria.

What testing tiers should I use for verifying web app features before shipping?▼

Web app verification offers three tiers: Quick for critical and high severity issues, Standard adding medium severity, and Exhaustive adding cosmetic checks. Each tier produces before and after health scores and a ship-readiness summary.

Does automated QA require existing test execution and commit tooling to work?▼

Yes, automated QA requires existing automated test execution to run suites, result collection to gather outcomes, and commit tooling to perform atomic bug fixes and subsequent re-verification on feature branches.

Can I run automated QA testing and generate a health score without applying fixes?▼

Yes, report-only mode generates health scores and ship-readiness summaries without committing atomic fixes. This mode runs automated tests and collects results to assess web application stability without modifying the codebase.

Related Skills

Explore More Software Engineering Skills→
benrapportbenrapport

qa

Automate end-to-end QA testing and bug fixing for web applications.

Community
Advanced
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

production-deployment-phase

Promote validated staging builds to production with semantic versioning and health checks.

Community
Advanced
aegnticaegntic
3

testing-automation

Automate unit, integration, and end-to-end test workflows with CI/CD integration.

Community
Advanced
sanskarbasnetsanskarbasnet
1

qa

Run end-to-end QA tests on web applications and document fixes.

Community
Advanced