qa

Execute Playwright browser, API, and CLI quality assurance with screenshot evidence.

204|14|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/garagon/nanostack --skill qa-garagon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/garagon/nanostack/tree/main/qa
Command: npx skills add https://github.com/garagon/nanostack --skill qa-garagon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright.

What problem does it solve?

Quality assurance and debugging that simulates real user behavior to find functional, visual, and integration bugs, then fixes them with verifiable, atomic changes so regressions are minimized.

Core Features & Use Cases

  • Multi-mode testing: Playwright-based browser testing, native GUI computer-use testing, API request checks, CLI execution tests, and targeted debug investigations.
  • Evidence-first workflow: Captures screenshots and structured results into qa/results, enforces prompt-injection boundaries, and saves artifacts for audit and autopilot continuation.
  • Operational guards: Mode-based intensity levels (quick, standard, thorough), explicit fix limits per mode, WTF-likelihood heuristics, and a required reproduce-isolate-fix-verify debug loop.

Quick Start

Run the QA suite on your local project with /qa --standard to execute browser, API, and CLI checks, capture screenshots, and save the results.

Frequently Asked Questions about qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate user-focused QA testing across browser, API, and CLI interfaces?

Playwright browser testing simulates real user behavior to find functional and visual bugs. It captures screenshot evidence into qa/results and applies atomic commits to fix regressions while minimizing side effects.

How do I debug and fix software bugs with atomic commits?

Debugging applies a reproduce-isolate-fix-verify loop to identify root causes and apply verifiable atomic changes. Mode-based intensity limits cap automated fixes to minimize regressions and ensure reproducible debugging steps.

Can I use Playwright for visual and native GUI testing?

Yes, Playwright enables browser-based visual testing while native GUI checks use computer-use testing. Both interfaces capture structured results and screenshot evidence into qa/results to verify functional and visual correctness.

What intensity modes are available for automated QA testing?

Automated QA testing supports quick, standard, and thorough mode-based intensity levels. Each mode enforces explicit fix limits and WTF-likelihood heuristics to control testing depth and cap applied automated fixes.

Does API testing work alongside CLI execution checks in an automated workflow?

API testing and CLI execution checks run together by executing HTTP API requests and CLI commands within the same QA workflow. Both check types save structured results and artifacts for audit and autopilot continuation.

How are prompt-injection boundaries handled during automated testing?

Prompt-injection boundaries are enforced during automated testing as an operational guard. The workflow satisfies these boundaries alongside mode-based intensity limits and artifact submission via save-artifact.sh.