qa

Tests web applications in a browser, fixes found bugs with atomic commits, and re-verifies.

107|7|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/no-session/pstack --skill qa-no-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/no-session/pstack/tree/main/qa
Command: npx skills add https://github.com/no-session/pstack --skill qa-no-session

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually clicking through a web app to find bugs is slow and easy to skip, and bugs that are found still need to be fixed, committed, and re-verified. This Skill automates the full loop: it drives a real browser through your app, catalogs issues by severity, fixes them in source code with atomic commits, and produces before/after evidence with a ship-readiness summary. ## Core Features & Use Cases - Browser-based QA testing: Navigates pages, clicks every interactive element, fills forms, checks console errors, and captures annotated screenshots across three tiers (Quick, Standard, Exhaustive). - Test-and-fix loop: Fixes bugs directly in source code with one atomic commit per fix, then re-verifies each fix with before/after screenshot evidence. - Diff-aware mode: On a feature branch with no URL given, analyzes the git diff to identify affected pages and routes, then tests exactly what changed. - Test framework bootstrap: Detects your runtime (Node, Ruby, Python, Go, Rust, PHP, Elixir), installs a test framework, writes real regression tests, and sets up CI. - Use Case: You just finished a billing feature on a branch. Run /qa and it detects your local dev server, tests the billing flow end-to-end, finds a broken form validation, fixes it, commits the fix, writes a regression test, and reports a health score improvement from 72 to 94. ## Quick Start Ask the AI to QA test the current feature branch and fix any bugs it finds, or provide a URL like http://localhost:3000 to test a running app.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automatically test my web app and fix bugs?

Run the qa skill against a URL or a feature branch. It drives a real browser through your pages, clicks interactive elements, checks console errors, then fixes found bugs in source code with one atomic commit per fix and re-verifies each one.

How do I test only the changes on my feature branch?

Run /qa on a feature branch without providing a URL. Diff-aware mode analyzes the git diff to identify affected pages, routes, and API endpoints, detects your local dev server on common ports, and tests exactly what changed.

What is the difference between Quick, Standard, and Exhaustive QA tiers?

The tiers control which severity of issues get fixed. Quick fixes critical and high severity only, Standard adds medium severity and is the default, and Exhaustive also fixes low and cosmetic issues.

Can it set up a test framework if my project has none?

Yes. It detects your runtime (Node, Ruby, Python, Go, Rust, PHP, or Elixir), researches current best practices, installs a framework like vitest or pytest, writes 3-5 real tests for recently changed code, and adds a GitHub Actions CI workflow.

Why does the QA skill require a clean git working tree?

Each bug fix gets its own atomic commit, so uncommitted changes would mix your work with automated fixes. The skill stops and offers to commit or stash your changes before starting.

What if I only want a QA report without automatic fixes?

Use the /qa-only variant for report-only mode. The main /qa skill always enters the test-fix-verify loop, while /qa-only produces the same structured report with health scores and issue taxonomy without modifying source code.