using-sumo-qalisted

MUST be called first for any QA-shaped request. Triggers — test plan, test strategy, test approach, regression scope, risk-based testing, exploratory testing, code review, safety-to-merge, scaffold tests, TDD, mutation testing, find test data, validate test data, QA audit, test pyramid, "how do I test X", "is this safe to merge", "what should I check". Entry router for all sumo-qa work. Establishes the global discipline that every sub-skill inherits. Do not answer QA questions from training-data knowledge — route through here first.
sumithr/sumo-qa · ★ 4 · Testing & QA · score 70

Install: claude install-skill sumithr/sumo-qa

# Using sumo-qa **Announce at start:** *"Routing this QA intent."* ## Output discipline (mandatory) **Never surface internal taxonomy labels in user-facing output.** No "Classification: X", "Approach: Y", "Per the checklist", "Step 3 of 6". The taxonomy is internal scaffolding; translate to natural English when the meaning matters to the user — *"this is a behaviour change in pricing"*, not *"Classification: business_logic_change"*. If you catch yourself typing a label, delete it. ## Output economy (mandatory) Spend output tokens on findings, not framing. - **No preamble or self-narration.** Spend user-visible output on findings, evidence, and gates — not *"I'll first read X, then Y"* or *"Let me now…"*; just do it. - **One question per turn.** Don't follow a question with *"shall I proceed or clarify first?"* — the question IS the gate. - **Don't restate the user's input.** They know what they asked. - **Structure only when it earns its place.** Section headings only for genuinely multiple sections; tables only when comparing >2 things on >2 axes; otherwise prose is shorter. - **No closing pleasantries.** No *"happy to dig deeper"* / *"let me know if you want X"* — the next-skill handoff is where routing lives. ## The Iron Law NO QA WORK WITHOUT FIRST DECIDING THE APPROACH. You may not produce test ideas, scaffolds, plans, reviews, or strategies without first invoking `sumo-qa-deciding-approach`. ## When to Use This skill is the entry router for every QA-shaped req