Open the app, test the flow, fix what breaks.
打开应用走完整流程，只修复已经验证的问题。
Best when browser QA needs to close the loop — find the bug, propose the fix, verify the fix, leave evidence. Where qa-loop emphasizes evidence trails for stakeholder reporting, gstack-qa emphasizes shipping the fix in the same session. Strongest on frontend refactors and visual regressions. Same screenshot data-risk caveat as qa-loop: don't point it at authenticated production sessions where the screenshot itself becomes a leak.
浏览器 QA 需要闭环时它最合适——找出 bug、提修复方案、验证修复、留下证据。qa-loop 偏向给干系人交证据，gstack-qa 偏向在同一个会话里把修复 ship 出去。在前端重构和视觉回归这两类场景上最强。截图数据风险和 qa-loop 一样——别对着有登录态的生产会话跑，截图本身就会变成泄漏面。
Use npx skills add to install this skill into the selected agent. Phase 0 commands are generated from source rules, not verified.
npx skills add https://github.com/garrytan/gstack/tree/main/qa -g -a codex -yDrop `-g` to install project-locally
Open the product, try the flow, fix what breaks, repeat.
Find the bugs, regressions, and missing tests first.
Sync the docs after the code changes, not three weeks later.
| this skill · 当前GStack QA | QA Loop | Review Radar | Docs Release | |
|---|---|---|---|---|
| Rating · 评分 | 4.8 | 4.9 | 4.8 | 4.7 |
| Stars · 星标 | 123k | 15k | 11k | 9.3k |
| Risk · 风险 | Medium risk · 中风险 | Medium risk · 中风险 | Low risk · 低风险 | Low risk · 低风险 |
| Best for · 最适合 | Browser regression loops | Browser smoke tests | Find the bugs, regressions, and missing tests first. | README updates |
| Not for · 不适合 | Read-only audit environments | Pure unit testing | Workflows that require stronger human review than this catalog entry documents. | Live deploy verification |