Open the product, try the flow, fix what breaks, repeat.
打开产品走一遍流程，发现问题就修，然后再验证。
Best browser QA pick when you need evidence to leave a paper trail. Each run produces screenshots, console diffs, and a reproducible action log — much harder for stakeholders to wave off than "I tested it locally." Works well as a pre-merge gate and for filing bugs with repro steps attached. Not for unit tests, and not for authenticated production sessions where the screenshot itself becomes a data risk.
做需要留证据链的浏览器 QA，它是最佳选择。每次跑都会产出截图、控制台 diff 和可重放的动作日志——比一句「我在本地测过了」更难被挡回去。适合做合并前关卡，也适合带证据提 bug。别用在单元测试场景，也别在敏感的登录态生产会话里用——截图本身就是数据风险。
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/anya-raghavan/qa-loop -g -a codex -yDrop `-g` to install project-locally
Open the app, test the flow, fix what breaks.
No fixes until the cause is real.
Find the bugs, regressions, and missing tests first.
| this skill · 当前QA Loop | GStack QA | Incident Investigate | Review Radar | |
|---|---|---|---|---|
| Rating · 评分 | 4.9 | 4.8 | 4.8 | 4.8 |
| Stars · 星标 | 15k | 123k | 10k | 11k |
| Risk · 风险 | Medium risk · 中风险 | Medium risk · 中风险 | Low risk · 低风险 | Low risk · 低风险 |
| Best for · 最适合 | Browser smoke tests | Open the app, test the flow, fix what breaks. | Root-cause analysis | Find the bugs, regressions, and missing tests first. |
| Not for · 不适合 | Pure unit testing | Workflows that require stronger human review than this catalog entry documents. | Quick cosmetic fixes | Workflows that require stronger human review than this catalog entry documents. |