qa-do
在需求模糊时快速指引合适技能，避免盲目调用
根据自然语言描述诊断 QA 情况并推荐应按序使用的 1–2 个技能。
把你一句话描述的 QA 问题快速诊断出匹配的测试流程，告诉你优先该用哪一到两个技能并按什么顺序跑。适合不知道从哪儿下手、问“我该先做什么测试”的场景，用来把模糊需求路由到具体工具和步骤。它不做深度指导，只做判断和推荐，帮你少走试错路线。
▸ 展开 SKILL.md 英文原文
Routing skill of last resort. Takes a plain-language QA situation and names the right 1-2 skills to use and in what order. Use ONLY when the request does not match any other skill's trigger phrases. Use when: "which skill should I use," "where do I start," "I'm not sure what to test," "/qa-do," or any vague QA situation that doesn't map to one skill. Not for: bootstrapping a brand-new project with no QA — use qa-start. Not for: capturing project setup/context — use qa-project-context. If the request clearly matches another skill, invoke that skill directly instead of routing through here. Related: qa-start, qa-project-context, test-strategy.
帮我安装这个 skill：https://raw.githubusercontent.com/petrkindlmann/qa-skills/main/skills/qa-do/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/petrkindlmann/qa-skills/main/skills/qa-do/SKILL.md"<objective> Most QA situations fit a recognizable pattern. This skill takes a plain-language description of what you're trying to do or what problem you're facing, matches it to a pattern, and names the 1-2 skills to use and in what order. It diagnoses and routes — it does not duplicate content from the skills it points to. If invoked with arguments, the situation is `$ARGUMENTS`; otherwise ask the user for a sentence or two describing it. </objective> ## Core Principles 1. **Route to the most precise skill, not the nearest neighbor.** A vague match to a broad skill is worse than a direct hit on a narrow one. "Reproduce this bug" goes to `bug-reproduction`, not the broader `ai-bug-tr