Test web applications and generate QA reports with health scores and screenshots.
npx skills add https://github.com/ligianehua/Gstack --skill qa-only-ligianehua
Please help me install this Agent Skill. Skill: qa-only Source: https://github.com/ligianehua/Gstack/tree/main/qa-only Command: npx skills add https://github.com/ligianehua/Gstack --skill qa-only-ligianehua
This Skill performs report-only QA testing. It systematically tests a web application and produces a structured report with a health score, screenshots, and reproducible steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when a bug report without code changes would be helpful.
Issue the /qa command on your target URL to start a report-only QA and review the health score, screenshots, and repro steps.
High-intent search queries and answers about installing and using this skill.
To generate a report-only QA check, run non-intrusive tests on your web application to produce a health score, evidence screenshots, and reproducible steps without applying any fixes. This structured report is suitable for sharing with stakeholders.
A health score in quality assurance reporting is a metric generated by systematically testing a web application to summarize its overall stability. It is accompanied by evidence screenshots and reproducible steps to document the current release-readiness state.
You can document reproducible steps and capture screenshots by performing structured non-intrusive browser automation tests on a web application. This process collects evidence and console logs to create a traceable bug report for QA handoffs.
You should use a report-only QA check when you need to surface bugs for release-readiness, create handoffs for QA teams, or provide a regression snapshot without altering production code. It performs structured tests but never applies fixes.
Yes, non-intrusive QA testing captures console logs alongside evidence screenshots and reproducible steps. This evidence collection ensures traceability and produces a consistent report format suitable for sharing with stakeholders.
Your QA report does not include code fixes because this approach is designed strictly for reporting issues. It performs non-intrusive tests to generate a health score and bug documentation, directing users to the full test-fix-verify loop for actual code changes.
NITISH-gitbitGuide exploratory QA testing of web applications through a structured workflow.
cattboyAutomate report-only QA testing for web applications with health scores and screenshots.
jonkikyRun report-only QA tests on a web application and generate a structured health report with screenshots and repro steps.
konneh-hubExplore web applications to find bugs and produce reports with screenshots and videos.
