What problem does it solve?
This Skill provides structured, report-only QA for web applications so teams can get evidence-driven bug reports without applying any fixes. It removes the manual work of clicking through flows, capturing screenshots, checking console errors, and writing repro steps so engineers and PMs can triage quickly.
Core Features & Use Cases
- Diff-aware testing: Scope tests to files changed on a feature branch and verify intended pages and routes.
- Multiple modes: Full systematic exploration, quick smoke tests, and regression comparisons against a saved baseline.
- Evidence-first reporting: Screenshots, before/after snapshots, console logs, health score, and exportable baseline JSON for CI or PR attachments.
- Auth and flows: Supports cookie import, scripted login flows, 2FA handling prompts, and clear guidance when manual CAPTCHA or human input is required.
- Use case: Run when a developer asks "just report bugs" on a branch or wants a non-invasive QA pass on a staging URL.
Quick Start
Ask gstack to run /qa-only against the current branch or provide a target URL to produce a report-only QA with screenshots, console logs, a health score, and reproducible steps.