Test web applications by exploring navigation paths and documenting bugs with annotated screenshots.
npx skills add https://github.com/gth-ai/hadriengayap.github.io --skill qa-gth-ai
Please help me install this Agent Skill. Skill: qa Source: https://github.com/gth-ai/hadriengayap.github.io/tree/main/.claude/skills/gstack/qa Command: npx skills add https://github.com/gth-ai/hadriengayap.github.io --skill qa-gth-ai
This Skill solves the inconsistency and lack of documentation in manual web application testing by providing a structured, repeatable, and evidence-based QA process.
Use the qa skill to perform a full systematic test on the website at https://hadriengayap.github.io.
High-intent search queries and answers about installing and using this skill.
Automate web application testing by using a skill that systematically explores navigation paths and validates interactive elements. It executes user-like interactions to identify functional, visual, and accessibility issues, generating structured health reports with clear reproduction steps.
Regression testing compares the current application state against a historical baseline to track improvements or regressions over time. It uses automated browser interactions to validate interactive elements and document any deviations from the established baseline.
Generate bug reports with annotated screenshots by running an automated QA process that systematically tests web applications. It documents discovered bugs with annotated screenshots, health scores, and clear reproduction steps for comprehensive evidence-based reporting.
Yes, you need a browser automation binary to perform automated smoke tests. This binary is required to execute user-like interactions, navigate web applications, validate interactive elements, and generate structured health reports during quick smoke tests or full-scale audits.
Yes, you can run a quick smoke test to check navigation paths and interactive elements. The testing process supports full-scale audits, quick smoke tests, and regression analysis by systematically exploring web applications and validating interactive elements.
The best way to document accessibility issues is through systematic web application testing that automatically navigates and audits web apps. It identifies functional, visual, and accessibility issues, generating evidence-based reports with annotated screenshots and reproduction steps.
hpuriRun E2E visual and interactive tests on ADK agents in a browser.
officebeatsTriage bug reports into engineering tickets with validated reproduction steps.
MFS-codeMeasure page load performance and compare metrics against saved baselines.
zerwizExplore web applications systematically and generate structured bug reports with evidence.
