gstack-qa

QA test web applications, find bugs, and fix them in atomic commits.

1|1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/tan-yong-sheng/GrowChat --skill gstack-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-qa
Source: https://github.com/tan-yong-sheng/GrowChat/tree/main/.claude/skills/gstack-qa
Command: npx skills add https://github.com/tan-yong-sheng/GrowChat --skill gstack-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA testing and bug fixing for web applications by systematically finding defects, validating fixes, and maintaining an auditable trail of changes.

Core Features & Use Cases

  • Automated and manual QA across frontend and backend, with repeatable tests and clear evidence.
  • Iterative bug fixing in source code, committing each fix atomically and re-verifying.
  • Proactive quality assurance guidance when issues are reported or new features are introduced.

Quick Start

Run QA on the current site with /qa to start testing and fixing bugs.

Frequently Asked Questions about gstack-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 application?

To automate QA testing and bug fixing, you can run a systematic process that tests your web app, finds defects, and fixes them in small atomic git commits with verifiable evidence.

How does iterative bug fixing with atomic commits work?

Iterative bug fixing with atomic commits works by verifying a defect, applying a fix to the source code, and committing that single change to git before re-running health checks to ensure the web app passes.

Do I need a git-based workflow to run e2e QA tests on my site?

Yes, you need a git-based workflow to run these e2e QA tests, as the process requires atomic commits for each bug fix, automated test runs, and verifiable before and after evidence to maintain quality.

What's the best way to maintain an auditable trail of bug fixes during regression testing?

The best way to maintain an auditable trail during regression testing is to commit each bug fix atomically in git, iterating until the web app passes all health checks with clear before and after evidence.

Can I run proactive quality assurance when new features are introduced to my web app?

Yes, you can run proactive quality assurance when new features are introduced, systematically validating the web app across frontend and backend with repeatable tests and clear evidence.