skills.rest
adryanmoldokkr32-pixel
adryanmoldokkr32-pixelCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

qa

Run tiered QA tests on web apps and commit fixes atomically.

Updated Apr 12, 2026
Search Tags:#automation#testing#qa#bug-fix#web-app#ship-readiness
One-click install
npx skills add https://github.com/adryanmoldokkr32-pixel/gstack --skill qa-adryanmoldokkr32-pixel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/adryanmoldokkr32-pixel/gstack/tree/main/qa
Command: npx skills add https://github.com/adryanmoldokkr32-pixel/gstack --skill qa-adryanmoldokkr32-pixel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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

  • Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic).
  • Produces before/after health scores, fix evidence, and a ship-readiness summary.
  • Proactively suggests QA or test opportunities when users describe readiness or issues.

Quick Start

Describe the web app you want tested and I will run a full QA pass, report findings, and verify 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 bug fixing for a web app?▼

Automated QA testing for a web app runs a full pass to identify bugs, iteratively applies source code fixes, and re-verifies the build. Each fix is committed atomically to ensure a stable, shippable state.

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

QA tiers differ by bug severity scope: Quick targets critical and high severity issues, Standard adds medium severity issues, and Exhaustive includes cosmetic issues to provide complete release readiness validation.

How do I test release readiness and get a ship-readiness summary?▼

Release readiness is tested by running an automated QA pass that outputs before and after health scores, provides fix evidence, and generates a final ship-readiness summary to validate if a build is ready to deploy.

Can I run a report-only QA test without automatically fixing bugs?▼

You can run a report-only QA test by using the /qa-only mode, which executes the testing pass and reports findings without iteratively modifying source code or committing atomic fixes.

When should I run regression tests during a development cycle?▼

Regression tests should be run during development cycles to validate builds and verify release readiness, proactively identifying bugs when a feature is described as ready for testing or reported as broken.

Related Skills

Explore More Software Engineering Skills→
curielmccurielmc

qa-only

Identify and summarize QA issues with screenshots and a health score.

Community
Advanced
shaythegay13shaythegay13

qa

QA test web applications, fix bugs, and commit fixes atomically.

Community
Advanced
henriquemeireles7henriquemeireles7

qa

Test web applications, fix bugs, and generate health scores with tiered QA.

Community
Advanced
ManzuetiManzueti

qa-only

Run automated QA tests on web applications and generate structured reports with health scores.

Community
Advanced