Automate tiered QA testing and atomic bug fixes for web applications.
npx skills add https://github.com/24601/gastack-pre-fork --skill qa-24601
Please help me install this Agent Skill. Skill: qa Source: https://github.com/24601/gastack-pre-fork/tree/main/qa Command: npx skills add https://github.com/24601/gastack-pre-fork --skill qa-24601
This Skill finds user-facing bugs in web applications, verifies regressions, and applies atomic fixes so features are reliably ship-ready. It reduces manual clicking, vague bug reports, and the churn of flaky releases by combining exploratory testing, automated checks, and code fixes into one workflow.
Run the QA workflow on your branch or URL by issuing /qa with a tier like --standard to test, fix high/medium issues, and generate a ship-readiness report.
High-intent search queries and answers about installing and using this skill.
Automate QA testing and bug fixing for web applications by running interactive and automated checks, applying targeted code fixes as atomic commits, and re-running verification to generate before/after evidence. This workflow reduces manual clicking and flaky releases.
Regression testing for branch diffs works by auto-detecting code changes and applying focused QA validation to those specific scopes. It runs tiered checks on local or deployed environments to verify regressions and produce ship-readiness reports.
Quick, Standard, and Exhaustive testing tiers differ by controlling the scope and severity of issues addressed. Users choose a tier like --standard to test features, fix high or medium issues, and generate a ship-readiness report based on the selected depth.
Yes, you can test a deployed web app by providing a URL. The QA workflow accepts a deployed URL to run interactive and automated checks, capture evidence like screenshots and console logs, and produce a structured report with health scores.
Outputs from an automated web app QA workflow include a structured QA report, before/after health scores, screenshots, console logs, and a fixes summary with commit SHAs and telemetry. These artifacts provide evidence of ship-readiness.
No, you do not need to handle browser CDP and authentication setup separately for test automation. The QA workflow handles auth, browser CDP, and test framework bootstrapping automatically as part of its end-to-end testing process.
cursorBuild or adapt local browser harnesses to verify UI behavior.
fghaffarAutomate end-to-end QA testing and atomic bug fixes for web applications.
zapabobMonitor file system changes and trigger quality analysis in real-time.
Jia-Hong-PengAutomate end-to-end QA testing and bug remediation for web applications.
