qa

Test web applications in a browser, fix discovered bugs, and commit verified fixes atomically.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/dhnpmp-tech/project-agent --skill qa-dhnpmp-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/dhnpmp-tech/project-agent/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/dhnpmp-tech/project-agent --skill qa-dhnpmp-tech

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 inconsistent, and bugs found often go unfixed or unverified. This Skill systematically QA tests a web application like a real user, fixes the bugs it finds in source code with atomic commits, and re-verifies each fix with before/after evidence. ## Core Features & Use Cases - Test → Fix → Verify Loop: Explores pages, clicks every interactive element, fills forms, checks console errors, then fixes confirmed bugs and re-tests them. - Three Severity Tiers: Quick (critical/high only), Standard (+ medium), and Exhaustive (+ low/cosmetic), with before/after health scores and a ship-readiness summary. - Diff-Aware Mode: On a feature branch with no URL, automatically scopes testing to pages and routes affected by the branch's changes. - Test Framework Bootstrap: Detects the project runtime, installs a test framework if missing, writes regression tests, and sets up CI. - Use Case: After shipping a new checkout flow on a feature branch, run /qa to have the branch's affected pages exercised end-to-end, bugs fixed with atomic commits, and a structured report with screenshots produced. ## Quick Start Ask the AI to QA test the current feature branch and fix any bugs it finds.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automatically test and fix bugs on a feature branch?

Run /qa on a feature branch without a URL to enter diff-aware mode. It analyzes the branch diff, identifies affected pages and routes, tests them in a browser, fixes confirmed bugs with atomic commits, and re-verifies each fix.

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

Quick fixes only critical and high severity issues, Standard additionally fixes medium severity issues, and Exhaustive also fixes low and cosmetic issues. Standard is the default tier.

Can I run QA testing without fixing the bugs found?

Yes, use /qa-only for report-only mode. The main /qa skill tests and fixes iteratively, while /qa-only produces the structured findings report without modifying source code.

Does the QA skill work if my project has no test framework?

Yes, it detects the project runtime and bootstraps a test framework if none exists, including installing packages, writing initial tests, creating a CI workflow, and documenting conventions in TESTING.md.

Why does /qa stop when my git working tree is dirty?

A clean working tree is required so each bug fix gets its own atomic commit. You are asked to commit or stash existing changes before QA begins, or abort to clean up manually.