Individual skill
qa
Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen. Three modes: browser (chromux/CDP, fast, DOM-level), computer (MCP computer-use, screenshot + pixel clicks, any app), and cli (tmux, send-keys + capture-pane for interactive terminals). Auto-selects mode or accepts --browser / --computer / --cli override. Use when asked to "qa", "QA", "test this site", "test this app", "find bugs", "test and fix", "fix what's broken", "dogfood", "exploratory test", "bug hunt", "QA this app", "사이트 테스트", "앱 테스트", "브라우저 QA", "화면 보고 테스트해줘", "네이티브 앱 테스트", "screen test". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.
skills/qa/SKILL.md
Source commit 7cff03298928d128c70c9ea45052102ba6b1a0ea
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 173
- Repository last updated
- May 21, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,338 bytesSKILL.mdcore · 10,338 bytesSKILL.mdcore · 10,338 bytesSKILL.mdcore · 10,338 bytesSKILL.mdcore · 10,338 bytesSKILL.mdcore · 10,338 bytesSKILL.mdcore · 10,338 bytesSKILL.mdcore · 10,338 bytesSKILL.mdcore · 10,338 bytesreferences/browser-mode.mddoc · 3,850 bytesreferences/browser-verify.mddoc · 5,755 bytesreferences/cli-mode.mddoc · 3,073 bytesreferences/computer-mode.mddoc · 3,045 bytesreferences/issue-taxonomy.mddoc · 3,613 bytesreferences/spec-drift-check.mddoc · 5,350 bytestemplates/qa-report-template.mddoc · 2,309 bytes
Read excerpt
# /qa: Plan -> Test -> Fix -> Verify
You are a QA engineer AND a bug-fix engineer. Test applications like a real user — click everything, fill every form, check every state. When you find bugs, fix them in source code with atomic commits, then re-verify. Produce a structured report with before/after evidence.
---
## Phase 0: Analyze Target & Select Mode
### 0.1 Parse User Request
| Parameter | Default | Override example |
|-----------|---------|-----------------|
| Target | (required) | URL, app name, CLI command, or "current branch" |
| Mode | auto-detect | `--browser`, `--computer`, `--cli` |