qa-do
Route a plain-language QA situation to the next 1-2 skills, then carry out the requested workflow with evidence and a readable report. 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," "validate this app," "run QA and report," "/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.
kindlmann · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add petrkindlmann/qa-skills --skill qa-do技能说明
name: qa-do description: >- Route a plain-language QA situation to the next 1-2 skills, then carry out the requested workflow with evidence and a readable report. 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," "validate this app," "run QA and report," "/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. license: MIT compatibility: Cross-tool skill instructions. The optional repository CLI requires Node 24; execution needs the project's test tools and any configured target. metadata: author: kindlmann version: "2.1" category: foundation argument-hint: "plain-language QA situation (e.g. 'our checkout flow is slow and tests are flaky')"
Discovery Questions
Check .agents/qa-project-context.md first. Inspect the project manifest, tests, current
changes, configured target, and available tools before asking anything. Ask only for a
missing target or requirement that changes the requested work.
Core Principles
-
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 broaderai-bug-triage; "test our Stripe checkout" goes topayment-testing, not genericapi-testing. When in doubt, prefer the skill whose trigger phrases name the exact artifact in the request. -
One or two skills, in order — never a pile. Output at most two skills. A second skill earns its place only when the first leaves a clear gap (diagnose → measure, risk → checklist). If one skill covers the request, say "Direct" and execute it. Routing to three skills means the situation is ambiguous — ask a clarifying question instead.
-
The routing table is the source of truth, and it goes stale. This router is uniquely prone to drift: every skill added to
skills/is a row that may be missing here. Regenerate the table and the Skill Categories reference againstskills/whenever a skill is added or removed. If a request has no row, fall back to the closest category in the Quick Reference rather than forcing a wrong direct match.
How to Use
Describe what you're trying to do or what problem you're facing — a sentence or two is
enough. The router outputs the recommended skill(s) (1-2, in order) and one line per
skill explaining the role it plays. Example: "Our E2E tests keep failing in CI but pass
locally." → test-reliability (diagnose flaky/environment-sensitive tests), then
ci-cd-integration (align the pipeline environment with local behavior).
Execute an Application Check
When the full repository is available, use its bounded runner. Resolve <qa-skills> to
this checkout and <project> to the application, even when the working directory differs.
node <qa-skills>/scripts/qa.mjs plan --project <project> --goal "<user goal>"
node <qa-skills>/scripts/qa.mjs run --project <project> --goal "<user goal>"
Read the primary skill and next relevant skill in the plan, then perform their workflows.
The runner discovers available test commands and writes report.html, result.json,
logs, and a host handoff. A plan is not an executed test. Where only individual skills
are installed, execute their recipes directly and retain equivalent evidence.
For URL checks, use a concrete target and application-owned readiness selector. Run the configured checks without treating optional missing integrations as a reason to stop unrelated local work. A missing browser, unavailable target, no observed tests, or an unreadable test result remains blocked or incomplete. Preserve skipped cases.
For a failure, reproduce it, preserve its assertion, and apply a repair only when it is
within the user's task. Execute again after changing the code. Stop after two attempts
if the failure persists and report the exact blocker; do not weaken an assertion or
retry indefinitely. The report covers executed checks, not universal correctness.
See the repository's docs/QA-RUNNER.md for configuration and host integration.
Common Situations and Their Skills
| Situation | Recommended Skills | Order |
|---|---|---|
| New project, no tests at all | qa-start (or qa-project-context → test-strategy) | Bootstrap the whole QA setup |
| Onboard a QA engineer to an existing codebase | qa-project-bootstrap | Direct — 30-day ramp + architecture audit |
| "Tests keep breaking in CI" | test-reliability → ci-cd-integration | Reliability first, then pipeline |
| "A UI refactor/redesign broke many selectors" | selector-drift-recovery | Direct — bulk regen, not per-test healing |
| "What should we test before this release?" | risk-based-testing → release-readiness | Risk first, then checklist |
| "We need Playwright tests" | playwright-automation | Direct |
| "We need Cypress tests" | cypress-automation | Direct |
| "Let an agent explore the app and assert outcomes" | agentic-browser-testing | Direct — goal-driven, no script |
| "Write tests from this PRD/spec/story" | ai-test-generation | Direc |