Automate web application testing and generate health reports with screenshots and repro steps.
npx skills add https://github.com/greencm/gstuck --skill qa-only-greencm
Please help me install this Agent Skill. Skill: qa-only Source: https://github.com/greencm/gstuck/tree/main/output/gstack/qa-only Command: npx skills add https://github.com/greencm/gstuck --skill qa-only-greencm
The QA-only skill automates the systematic testing of web applications and provides detailed reports without the ability to fix issues, helping you quickly identify problems for further action.
Run a QA test report for your project by invoking: "qa report only"
High-intent search queries and answers about installing and using this skill.
Automated web app testing reports without fixes are generated by systematically testing pages with a headless browser to identify issues. This skill provides structured health reports, complete with screenshots and repro steps, intended for initial QA passes before development proceeds to the fix phase.
A QA health report for web applications includes a calculated health score indicating overall status, screenshots of tested pages for visual verification, and detailed repro steps to replicate detected issues. This structured report helps developers quickly identify and address problems for further action.
Yes, you can use a headless browser to capture screenshots and generate repro steps for bug detection. The skill leverages headless browser testing to automate web page interactions, documenting visual states and providing systematic steps to replicate any identified issues.
Yes, a working Conductor session or an interactive prompt is required to run automated web testing for full functionality. The skill depends on this environment to properly execute headless browser testing and generate health reports for your web application.
Puppeteer works with this skill as a core dependency to perform web app health checking. It drives the headless browser to automate testing of web pages, enabling the skill to capture screenshots and detect bugs systematically during the QA reporting process.
The primary limitation of using QA-only for bug detection is that it generates reports without applying any fixes. It is strictly intended for initial quality assurance passes to identify issues, requiring a separate development phase to actually resolve the detected bugs.
AIDotNetAutomate headless Chrome tasks for PDF generation, screenshots, and web scraping.
bajajvinamrIdentify and document web application defects with reproducible steps and screenshots.
johnlindquistAutomate browser interactions for web testing and data extraction with Puppeteer or Playwright.
limzivectorExecute automated QA tests and suggest bug fixes for web applications.
